From: Srinivas Kandagatla <srini@kernel.org>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
alice.guo@oss.nxp.com
Cc: devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Alice Guo <alice.guo@nxp.com>,
Conor Dooley <conor.dooley@microchip.com>,
Peng Fan <peng.fan@nxp.com>, Frank Li <Frank.Li@nxp.com>
Subject: Re: (subset) [PATCH v2 0/3] Add i.MX94 OCOTP support
Date: Mon, 10 Nov 2025 07:53:11 +0000 [thread overview]
Message-ID: <176276119135.18911.11093560408618836361.b4-ty@kernel.org> (raw)
In-Reply-To: <20251020-imx94-v1-0-0b4b58a57bf9@nxp.com>
On Mon, 20 Oct 2025 18:50:41 +0800, alice.guo@oss.nxp.com wrote:
> This patch series adds support for the OCOTP controller on the i.MX94
> SoC. The OCOTP controller provides access to eFuse regions.
>
> Tested on an i.MX943 EVK board with successful NVMEM read access via
> sysfs.
>
> Changes for v2:
> - improved commit messages for each patch
> - added Acked-by and Reviewed-by tags from reviewers
> - updated the efuse@47510000 node
>
> [...]
Applied, thanks!
[1/3] dt-bindings: nvmem: imx-ocotp: Add support for i.MX94
commit: 294e0add7bb8eca991f7e8d064c71acfffd10462
[2/3] nvmem: imx-ocotp-ele: Add i.MX94 OCOTP support
commit: 9e8d7c3115f4eceaae2d5282518be78bcb7ca188
Best regards,
--
Srinivas Kandagatla <srini@kernel.org>
prev parent reply other threads:[~2025-11-10 7:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 10:50 [PATCH v2 0/3] Add i.MX94 OCOTP support alice.guo
2025-10-20 10:50 ` [PATCH v2 1/3] dt-bindings: nvmem: imx-ocotp: Add support for i.MX94 alice.guo
2025-10-20 10:50 ` [PATCH v2 2/3] nvmem: imx-ocotp-ele: Add i.MX94 OCOTP support alice.guo
2025-10-20 10:50 ` [PATCH v2 3/3] arm64: dts: imx94: Add OCOTP node alice.guo
2025-10-21 15:51 ` Frank Li
2025-11-10 7:53 ` Srinivas Kandagatla [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=176276119135.18911.11093560408618836361.b4-ty@kernel.org \
--to=srini@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=alice.guo@nxp.com \
--cc=alice.guo@oss.nxp.com \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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