Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Frank Li <Frank.li@oss.nxp.com>
To: Frieder Schrempf <frieder.schrempf@kontron.de>
Cc: Frank Li <Frank.Li@nxp.com>, Jonathan Corbet <corbet@lwn.net>,
	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>,
	Pankaj Gupta <pankaj.gupta@nxp.com>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org, imx@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org
Subject: Re: (subset) [PATCH v25 0/7] firmware: imx: driver for NXP secure-enclave
Date: Tue, 14 Jul 2026 09:38:04 -0500	[thread overview]
Message-ID: <alZJzKHs8w0UAw_z@SMW015318> (raw)
In-Reply-To: <73a5b9fd-aff4-4ae2-ab2b-d860bbc7325d@kontron.de>

On Tue, Jul 14, 2026 at 09:27:06AM +0200, Frieder Schrempf wrote:
> On 05.05.26 17:53, Frank Li wrote:
> >
> > On Thu, 22 Jan 2026 17:19:12 +0530, Pankaj Gupta wrote:
> >> The NXP's i.MX EdgeLock Enclave, a HW IP creating an embedded secure
> >> enclave within the SoC boundary to enable features like
> >> - HSM
> >> - SHE
> >> - V2X
> >>
> >> Communicates via message unit with linux kernel. This driver is
> >> enables communication ensuring well defined message sequence protocol
> >> between Application Core and enclave's firmware.
> >>
> >> [...]
> >
> > Applied, thanks!
> >
> > [1/7] Documentation/firmware: add imx/se to other_interfaces
> >       commit: 3b4531c6e0f4c8874f0266853a410438eda1fc24
> > [2/7] dt-bindings: arm: fsl: add imx-se-fw binding doc
> >       commit: 4d7bcf0869686d7d7fbf16244453b987e5ca6d14
> > [3/7] firmware: imx: add driver for NXP EdgeLock Enclave
> >       commit: 338529a73c2bf2c277013b745cfe6f19b84b70af
> > [4/7] firmware: imx: device context dedicated to priv
> >       commit: 2d733ed67f608ee85abb854157011f88d7f280a8
> > [5/7] firmware: drivers: imx: adds miscdev
> >       commit: 4de71839142b5f43846e3593f4eb236e1d733885
> What happened to these patches?
>
> They were part of linux-next for quite some time (up to next-20260630)
> and then they disappeared (missing in next-20260701).
>
> I didn't find any hint where or why they were dropped.

Sashiko and linux-next build found some issues, which need be fixed before
send pull request.

Pankaj is working on the new version.

Frank

>


  reply	other threads:[~2026-07-14 14:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-22 11:49 [PATCH v25 0/7] firmware: imx: driver for NXP secure-enclave Pankaj Gupta
2026-01-22 11:49 ` [PATCH v25 1/7] Documentation/firmware: add imx/se to other_interfaces Pankaj Gupta
2026-01-22 11:49 ` [PATCH v25 2/7] dt-bindings: arm: fsl: add imx-se-fw binding doc Pankaj Gupta
2026-01-22 11:49 ` [PATCH v25 3/7] firmware: imx: add driver for NXP EdgeLock Enclave Pankaj Gupta
2026-02-24 10:49   ` Frieder Schrempf
2026-02-24 11:16   ` Frieder Schrempf
2026-01-22 11:49 ` [PATCH v25 4/7] firmware: imx: device context dedicated to priv Pankaj Gupta
2026-01-22 11:49 ` [PATCH v25 5/7] firmware: drivers: imx: adds miscdev Pankaj Gupta
2026-05-06 21:18   ` Arnd Bergmann
2026-01-22 11:49 ` [PATCH v25 6/7] arm64: dts: imx8ulp: add secure enclave node Pankaj Gupta
2026-01-22 11:49 ` [PATCH v25 7/7] arm64: dts: imx8ulp-evk: add reserved memory property Pankaj Gupta
2026-01-29 16:58 ` [PATCH v25 0/7] firmware: imx: driver for NXP secure-enclave Pankaj Gupta
2026-02-24 11:18   ` Frieder Schrempf
2026-04-21  7:52     ` Frieder Schrempf
2026-04-21  8:57       ` Frank Li
2026-05-05 15:53 ` (subset) " Frank Li
2026-07-14  7:27   ` Frieder Schrempf
2026-07-14 14:38     ` Frank Li [this message]
2026-07-15  7:32       ` Frieder Schrempf

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=alZJzKHs8w0UAw_z@SMW015318 \
    --to=frank.li@oss.nxp.com \
    --cc=Frank.Li@nxp.com \
    --cc=conor+dt@kernel.org \
    --cc=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=frieder.schrempf@kontron.de \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pankaj.gupta@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