From: Tan Siewert <tan.siewert@9elements.com>
To: Prasanth Kumar Padarthi <prasanth.padarthi10@gmail.com>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
joel@jms.id.au, andrew@codeconstruct.com.au,
ryan_chen@aspeedtech.com, billy_tsai@aspeedtech.com,
neal_liu@aspeedtech.com, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
srini@kernel.org
Subject: Re: [PATCH v2 0/2] nvmem: aspeed: Add read-only AST2600 OTP support
Date: Fri, 20 Nov 2026 19:58:01 +0100 [thread overview]
Message-ID: <9519e889-8c78-485c-a31d-28df8b7cecc3@9elements.com> (raw)
In-Reply-To: <20261120174440.123487-1-prasanth.padarthi10@gmail.com>
On 11/20/26 6:44 PM, Prasanth Kumar Padarthi wrote:
> Hi,
>
> This series exposes permitted AST2600 OTP data through root-only NVMEM
> for userspace diagnostics using raw offsets. It adds the SBC NVMEM
> binding and a read-only driver adapted from ASPEED's downstream driver.
>
> Changes since v1:
> - Add the separate binding patch and rename the driver nvmem-aspeed-otp.
> - Poll once after a 1-us delay; retain the 100-ms timeout and log failures.
> - Initialize read mode once at probe and stop commands after a timeout.
> - Use a fixed secure-prefix keepout and check the live SEC54 range on reads.
> - Simplify copying, locking, configuration and Kconfig help.
>
> Tested on B650D4U (AST2600 A3), OpenBMC Linux 6.18.24 and upstream-based
> Linux 7.4-rc1: repeated reads, cross-pair reads and 40 reads from four
> concurrent readers passed. A 12-byte range matched the saved ASPEED-derived
> reference fingerprint. The 7.4-rc1 RAM boot used the working OpenBMC DTB
> and initramfs and also passed the final-pair comparison. ARM zImage built
> successfully.
>
> AI assisted with driver revisions, validation tooling and patch text,
> using the downstream code, review comments and Neal's hardware guidance.
> Hardware tests were run by the submitter.
>
> Prasanth Kumar Padarthi (2):
> dt-bindings: arm: aspeed: sbc: Describe OTP NVMEM provider
> nvmem: aspeed: Add read-only AST2600 OTP support
>
> base-commit: 6628e7d4c6b25c8d18f1345e3a20d21829aae7e4
Again, please fix your threading... Other maintainers and reviewers
already told you in other threads that sending a new revision must not
be "In-reply-to" to the previous revision. See the "Explicit In-Reply-To
headers" section of the submission documentation [1].
Consider the use of b4 [2], which can handle it more consistently.
Tan
[1]
https://docs.kernel.org/process/submitting-patches.html#explicit-in-reply-to-headers
[2] https://b4.docs.kernel.org/en/latest/
prev parent reply other threads:[~2026-11-20 18:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 3:42 [PATCH v1 0/1] " Prasanth Kumar Padarthi
2026-11-13 3:42 ` [PATCH v1 1/1] " Prasanth Kumar Padarthi
2026-11-13 13:05 ` Tan Siewert
2026-11-14 13:21 ` Prasanth
2026-11-20 17:44 ` [PATCH v2 0/2] " Prasanth Kumar Padarthi
2026-11-20 17:44 ` [PATCH v2 1/2] dt-bindings: arm: aspeed: sbc: Describe OTP NVMEM provider Prasanth Kumar Padarthi
2026-11-20 17:44 ` [PATCH v2 2/2] nvmem: aspeed: Add read-only AST2600 OTP support Prasanth Kumar Padarthi
2026-11-20 19:05 ` Tan Siewert
2026-11-20 18:58 ` Tan Siewert [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=9519e889-8c78-485c-a31d-28df8b7cecc3@9elements.com \
--to=tan.siewert@9elements.com \
--cc=andrew@codeconstruct.com.au \
--cc=billy_tsai@aspeedtech.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neal_liu@aspeedtech.com \
--cc=prasanth.padarthi10@gmail.com \
--cc=robh@kernel.org \
--cc=ryan_chen@aspeedtech.com \
--cc=srini@kernel.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
all inboxes | Powered by JetHome®