From: Frank Li <Frank.li@oss.nxp.com>
To: Frieder Schrempf <frieder@fris.de>
Cc: Srinivas Kandagatla <srini@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Frank Li <Frank.Li@nxp.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Shawn Guo <shawnguo@kernel.org>,
Pankaj Gupta <pankaj.gupta@nxp.com>,
"Peng Fan (OSS)" <peng.fan@oss.nxp.com>,
devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux@ew.tq-group.com,
Frieder Schrempf <frieder.schrempf@kontron.de>,
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Subject: Re: [PATCH v4 00/11] Support ELE API in i.MX OCOTP NVMEM driver
Date: Mon, 27 Jul 2026 09:42:59 -0500 [thread overview]
Message-ID: <amduc2ISVquBlD8c@SMW015318> (raw)
In-Reply-To: <20260727-upstreaming-next-20260609-imx-ocotp-ele-v4-0-1a515de33093@kontron.de>
On Mon, Jul 27, 2026 at 03:00:43PM +0200, Frieder Schrempf wrote:
...
>
> ---
> Frieder Schrempf (11):
> dt-bindings: nvmem: imx-ocotp: Add support for secure-enclave
> firmware: imx: ele: Fix indentation in ele_base_msg.h
> firmware: imx: ele: Export API functions
Srinivas Kandagatl:
There are depedence with firmware ele. what's plan to pick this
patch set?
Will you take firmware: imx: ele: with my Ack/review-by?
Frank
prev parent reply other threads:[~2026-07-27 14:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 13:00 [PATCH v4 00/11] Support ELE API in i.MX OCOTP NVMEM driver Frieder Schrempf
2026-07-27 13:00 ` [PATCH v4 01/11] dt-bindings: nvmem: imx-ocotp: Add support for secure-enclave Frieder Schrempf
2026-07-27 13:00 ` [PATCH v4 02/11] firmware: imx: ele: Fix indentation in ele_base_msg.h Frieder Schrempf
2026-07-27 13:00 ` [PATCH v4 03/11] firmware: imx: ele: Export API functions Frieder Schrempf
2026-07-27 13:00 ` [PATCH v4 04/11] nvmem: imx-ocotp-ele: Add keepout table for i.MX93 Frieder Schrempf
2026-07-27 13:00 ` [PATCH v4 05/11] nvmem: imx-ocotp-ele: Remove device-specific reg_read() Frieder Schrempf
2026-07-27 13:00 ` [PATCH v4 06/11] nvmem: imx-ocotp-ele: Use scope-based cleanup helpers in imx_ocotp_reg_read() Frieder Schrempf
2026-07-27 13:00 ` [PATCH v4 07/11] nvmem: imx-ocotp-ele: Support the ELE API Frieder Schrempf
2026-07-27 13:00 ` [PATCH v4 08/11] nvmem: imx-ocotp-ele: Remove the FUSE_ELE type Frieder Schrempf
2026-07-27 13:00 ` [PATCH v4 09/11] nvmem: imx-ocotp-ele: Rename FSB access map Frieder Schrempf
2026-07-27 13:00 ` [PATCH v4 10/11] arm64: dts: Add ELE firmware node and common include Frieder Schrempf
2026-07-27 13:00 ` [PATCH v4 11/11] arm64: dts: Enable EdgeLock Secure Enclave on all i.MX91/i.MX93 boards Frieder Schrempf
2026-07-27 14:42 ` Frank Li [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=amduc2ISVquBlD8c@SMW015318 \
--to=frank.li@oss.nxp.com \
--cc=Frank.Li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=frieder.schrempf@kontron.de \
--cc=frieder@fris.de \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@ew.tq-group.com \
--cc=pankaj.gupta@nxp.com \
--cc=peng.fan@oss.nxp.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.