Re: [PATCH v51 5/7] firmware: imx: adds miscdev

From: Frank Li

Date: Wed Nov 18 2026 - 10:54:08 EST


On Wed, Nov 18, 2026 at 03:43:28PM +0100, Frieder Schrempf wrote:
> On 18.11.26 13:46, Frieder Schrempf wrote:
> > +Cc: Peng
> >
> > Hi NXP developers,
> >
> > On 05.10.26 16:28, Frieder Schrempf wrote:
> >> On 16.09.26 16:39, Frank Li wrote:
> >>> On Wed, Sep 16, 2026 at 03:16:13PM +0200, Arnd Bergmann wrote:
> >>>> On Mon, Sep 14, 2026, at 21:40, pankaj.gupta@xxxxxxxxxxx wrote:
> >>>>> From: Pankaj Gupta <pankaj.gupta@xxxxxxx>
> >>>>>
> >>>>> Adds the driver for communication interface to secure-enclave, that
> >>>>> enables exchanging messages with NXP secure enclave HW IP(s)
> >>>>> like EdgeLock Enclave, from:
> >>>>> - User-Space Applications via character driver.
> >>>>>
> >>>>> ABI documentation for the NXP secure-enclave driver.
> >>>>
> >>>> I just saw this in linux-next, where it has caused a build failure
> >>>> for a missing include of linux/slab.h. I hadn't see the series
> >>>> before (even though it is a v51, which seems crazy), but I am
> >>>
> >>> It is in linux-next about v37, but build bot find many problems, I dropped
> >>> it and request to fix it. And sashiko is online recently and also find many
> >>> risk. I request to clean up it, and local AI environment have difference
> >>> with sashiko, so bump to v51.
> >>>
> >>> I put to linux-next again to make sure that pass all build test.
> >>>
> >>> Other two problems, need more time to check whole review history. reply
> >>> you later.
> >>
> >> So this is still in linux-next, but was not sent in the pull request for
> >> 7.4. It's rather confusing to me that maintainers add stuff to
> >> linux-next for build-testing and then leave it there, neither removing
> >> it, nor continuing the mainlining process.
> >>
> >> Frank, what is the plan?
> >>
> >> I'm currently rebasing my work for the NVMEM driver onto linux-next, but
> >> as there have been so many iterations and this whole thing took so long,
> >> I want to make sure that this is not another dead end where I'm wasting
> >> my time on.
> >
> > I need to ping here, again. What is the plan at NXP to move on with
> > this? This is blocking multiple features that depend on ELE firmware
> > support for i.MX9 and similar platforms from being upstreamed.
> To be more constructive, here is a proposal: let's get the
> kernel-internal part of this series merged first (patch 2-4, DT patches
> 6-7, doc patch 1 reduced to kernel side). I currently don't see any
> objections or issues with those.
>
> This would unblock drivers using the in-kernel API, such as the NVMEM
> driver and this is also the part I already tested when working on [1].
>
> The somewhat more controversial uAPI in patch 5 can then be further
> discussed until there is a consensus on it.
>
> Arnd, Frank, would that work for you?

It needs at least one user for the in-kernel API.

Frank

>
> Pankaj, can you prepare such a reduced series?
>
> [1]
> https://patchwork.kernel.org/project/linux-arm-kernel/cover/20260727-upstreaming-next-20260609-imx-ocotp-ele-v4-0-1a515de33093@xxxxxxxxxx/