From: Peter Maydell <peter.maydell@linaro.org>
To: Rayhan Faizel <rayhan.faizel@gmail.com>
Cc: qemu-devel@nongnu.org, philmd@linaro.org, qemu-arm@nongnu.org
Subject: Re: [PATCH v3 0/3] Initial support for One-Time Programmable Memory (OTP) in BCM2835
Date: Thu, 30 May 2024 14:27:02 +0100 [thread overview]
Message-ID: <CAFEAcA_zBhe+HxOqtAzWSCbzApEhknr+NeheA1uLj641EXMM5w@mail.gmail.com> (raw)
In-Reply-To: <20240519094106.2142896-1-rayhan.faizel@gmail.com>
On Sun, 19 May 2024 at 10:42, Rayhan Faizel <rayhan.faizel@gmail.com> wrote:
>
> All BCM2835 boards have on-board OTP memory with 66 32-bit rows. Usually,
> its contents are accessible via mailbox commands.
>
> [Changes in v3]
>
> - Forgot to replace constant with macro in one particular spot.
>
> [Changes in v2]
>
> - Replace read/write with get/set in bcm2835_otp.c.
> - Use impl instead of valid in bcm2835_otp.c.
> - Replace all constant values with macros defined in bcm2835_otp.h.
> - Change memory region size of OTP device to 0x80.
> - After further testing on a real Raspberry Pi 3, I noticed a few things
> contrary to my initial assumptions:
> -- The customer OTP lock bit is bit 6 of row 32, NOT bit 30 of row 30. This is
> currently undocumented to my knowledge.
> -- The above lock indeed applies to the private key as well.
>
> Rayhan Faizel (3):
> hw/nvram: Add BCM2835 OTP device
> hw/arm: Connect OTP device to BCM2835
> hw/misc: Implement mailbox properties for customer OTP and device
> specific private keys
Applied to target-arm.next, thanks.
-- PMM
next prev parent reply other threads:[~2024-05-30 13:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-19 9:41 [PATCH v3 0/3] Initial support for One-Time Programmable Memory (OTP) in BCM2835 Rayhan Faizel
2024-05-19 9:41 ` [PATCH v3 1/3] hw/nvram: Add BCM2835 OTP device Rayhan Faizel
2024-05-30 12:29 ` Peter Maydell
2024-05-19 9:41 ` [PATCH v3 2/3] hw/arm: Connect OTP device to BCM2835 Rayhan Faizel
2024-05-30 12:29 ` Peter Maydell
2024-05-19 9:41 ` [PATCH v3 3/3] hw/misc: Implement mailbox properties for customer OTP and device specific private keys Rayhan Faizel
2024-05-30 12:32 ` Peter Maydell
2024-05-30 13:27 ` Peter Maydell [this message]
2024-06-24 9:12 ` [PATCH v3 0/3] Initial support for One-Time Programmable Memory (OTP) in BCM2835 Rayhan Faizel
2024-06-24 10:22 ` Peter Maydell
2024-06-24 17:36 ` Rayhan Faizel
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=CAFEAcA_zBhe+HxOqtAzWSCbzApEhknr+NeheA1uLj641EXMM5w@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=rayhan.faizel@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).