mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Barebox List <barebox@lists.infradead.org>,
	 Sascha Hauer <s.hauer@pengutronix.de>
Subject: Re: [PATCH] nvmem: rockchip-otp: implement SoC UID reading
Date: Fri, 20 Mar 2026 07:35:54 +0100	[thread overview]
Message-ID: <177398855462.351287.18077361694020239743.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20260317134755.3184029-1-s.hauer@pengutronix.de>


On Tue, 17 Mar 2026 14:47:55 +0100, Sascha Hauer wrote:
> The Rockchip SoCs supported by the rockchip-otp driver have a SoC UID in
> the OTP data. Read it out and forward it to barebox. The raw SoC UID
> goes through some crc32 code before it is used. This is based on U-Boot
> code which itself is based on the Rockchip Downstream Linux support.
> 
> 

Applied, thanks!

[1/1] nvmem: rockchip-otp: implement SoC UID reading
      https://git.pengutronix.de/cgit/barebox/commit/?id=101b25168f3c (link may not be stable)

Best regards,
-- 
Sascha Hauer <s.hauer@pengutronix.de>




      parent reply	other threads:[~2026-03-20  6:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-17 13:47 Sascha Hauer
2026-03-17 21:44 ` Marco Felsch
2026-03-18 10:32   ` Sascha Hauer
2026-03-20  6:35 ` Sascha Hauer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=177398855462.351287.18077361694020239743.b4-ty@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox