From: Frank Li <Frank.li@nxp.com>
To: "Alice Guo (OSS)" <alice.guo@oss.nxp.com>
Cc: Srinivas Kandagatla <srini@kernel.org>,
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>,
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>
Subject: Re: [PATCH v1 1/3] dt-bindings: nvmem: imx-ocotp: Add binding for i.MX94
Date: Wed, 24 Sep 2025 10:42:46 -0400 [thread overview]
Message-ID: <aNQDZqHDIw7RLLfk@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20250924-imx943-v1-1-0d32d7852ecb@oss.nxp.com>
On Wed, Sep 24, 2025 at 06:06:23PM +0800, Alice Guo (OSS) wrote:
> From: Alice Guo <alice.guo@nxp.com>
Subject needn't "binding" again.
dt-bindings: nvmem: imx-ocotp: Add compatible string fsl,imx94-ocotp
or Add i.MX94 support.
Frank
>
> Update the imx-ocotp device tree binding documentation to include
> support for the i.MX94 SoC.
>
> Signed-off-by: Alice Guo <alice.guo@nxp.com>
> ---
> Documentation/devicetree/bindings/nvmem/imx-ocotp.yaml | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/nvmem/imx-ocotp.yaml b/Documentation/devicetree/bindings/nvmem/imx-ocotp.yaml
> index b2cb76cf9053..a8076d0e2737 100644
> --- a/Documentation/devicetree/bindings/nvmem/imx-ocotp.yaml
> +++ b/Documentation/devicetree/bindings/nvmem/imx-ocotp.yaml
> @@ -14,7 +14,8 @@ maintainers:
> description: |
> This binding represents the on-chip eFuse OTP controller found on
> i.MX6Q/D, i.MX6DL/S, i.MX6SL, i.MX6SX, i.MX6UL, i.MX6ULL/ULZ, i.MX6SLL,
> - i.MX7D/S, i.MX7ULP, i.MX8MQ, i.MX8MM, i.MX8MN i.MX8MP and i.MX93/5 SoCs.
> + i.MX7D/S, i.MX7ULP, i.MX8MQ, i.MX8MM, i.MX8MN i.MX8MP, i.MX93, i.MX94,
> + and i.MX95.
>
> allOf:
> - $ref: nvmem.yaml#
> @@ -36,6 +37,7 @@ properties:
> - fsl,imx8mq-ocotp
> - fsl,imx8mm-ocotp
> - fsl,imx93-ocotp
> + - fsl,imx94-ocotp
> - fsl,imx95-ocotp
> - const: syscon
> - items:
>
> --
> 2.43.0
>
next prev parent reply other threads:[~2025-09-24 14:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-24 10:06 [PATCH 0/3] Add i.MX94 OCOTP support Alice Guo (OSS)
2025-09-24 10:06 ` [PATCH v1 1/3] dt-bindings: nvmem: imx-ocotp: Add binding for i.MX94 Alice Guo (OSS)
2025-09-24 14:42 ` Frank Li [this message]
2025-09-24 19:14 ` Conor Dooley
2025-09-24 10:06 ` [PATCH v1 2/3] nvmem: imx-ocotp-ele: Add support for i.MX94 OCOTP Alice Guo (OSS)
2025-09-24 14:43 ` Frank Li
2025-09-24 10:06 ` [PATCH v1 3/3] arm64: dts: imx94: Add OCOTP node Alice Guo (OSS)
2025-09-24 14:44 ` Frank Li
2025-09-25 1:18 ` [PATCH 0/3] Add i.MX94 OCOTP support Rob Herring (Arm)
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=aNQDZqHDIw7RLLfk@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=alice.guo@nxp.com \
--cc=alice.guo@oss.nxp.com \
--cc=conor+dt@kernel.org \
--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=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--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