From: Frieder Schrempf <frieder.schrempf@kontron.de>
To: Pankaj Gupta <pankaj.gupta@nxp.com>,
"Frank Li (OSS)" <frank.li@oss.nxp.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
"Pankaj Gupta (OSS)" <pankaj.gupta@oss.nxp.com>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.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>,
Randy Dunlap <rdunlap@infradead.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"imx@lists.linux.dev" <imx@lists.linux.dev>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Peng Fan <peng.fan@nxp.com>
Subject: Re: [EXT] Re: [PATCH v51 5/7] firmware: imx: adds miscdev
Date: Thu, 19 Nov 2026 19:49:33 +0100 [thread overview]
Message-ID: <463b3707-4126-4f32-990e-e8f02d278695@kontron.de> (raw)
In-Reply-To: <GV2PR04MB12271E129EDA863074E4807B895792@GV2PR04MB12271.eurprd04.prod.outlook.com>
On 19.11.26 18:47, Pankaj Gupta wrote:
>>>>>>>
>>>>>>> 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.
>>
>> I can provide the NVMEM driver as user. I just need to rebase my series on the
>> new reduced firmware driver patchset once that has been posted.
>>
>> Or if you want to have this all in one series, maybe someone at NXP
>> (Pankaj?) can provide the firmware driver as proposed above in a public git tree
>> somewhere or send it as RFC. Then I will provide the NVMEM patches on top of
>> this for you to pick up and send in a combined series.
>>
>> Just let me know what works best for you.
>>
>>>>
>>>> Pankaj, can you prepare such a reduced series?
>
> Hi Frieder,
>
> Thanks for the proposal, and sorry that you had to ping more than once.
>
> Yes, I will prepare the reduced series as you describe:
>
> - patches 2-4 (in-kernel interface only),
> - DT patches 6-7,
> - patch 1 cut down to the kernel side,
> - patch 5 (the uAPI / character device) dropped from this series. It
> will be posted separately so the uAPI discussion can continue
> without blocking the in-kernel users.
>
> It will include an in-kernel user from our side, OCOTP/NVMEM support
> for i.MX8ULP, and I will make it available on a public branch so you
> have a fixed base to rebase your i.MX93 NVMEM series [1] onto.
>
> I will reply here with the links once it is out.
Ok, great! Thanks!
If you include the OCOTP NVMEM driver for i.MX8ULP, feel free to pick up
and adapt patches from my v4 patchset [1]. Especially patch 7 [2] might
be what you would also need.
[1]
https://patchwork.kernel.org/project/linux-arm-kernel/cover/20260727-upstreaming-next-20260609-imx-ocotp-ele-v4-0-1a515de33093@kontron.de/
[2]
https://patchwork.kernel.org/project/linux-arm-kernel/patch/20260727-upstreaming-next-20260609-imx-ocotp-ele-v4-7-1a515de33093@kontron.de/
next prev parent reply other threads:[~2026-11-19 18:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 19:39 [PATCH v51 0/7] firmware: imx: driver for NXP secure-enclave pankaj.gupta
2026-09-14 19:39 ` [PATCH v51 1/7] Documentation/firmware: add imx/se to other_interfaces pankaj.gupta
2026-09-14 19:39 ` [PATCH v51 2/7] dt-bindings: arm: fsl: add imx-se-fw binding doc pankaj.gupta
2026-09-14 19:40 ` [PATCH v51 3/7] firmware: imx: add driver for NXP EdgeLock Enclave pankaj.gupta
2026-09-14 19:40 ` [PATCH v51 4/7] firmware: imx: device context dedicated to priv pankaj.gupta
2026-09-14 19:40 ` [PATCH v51 5/7] firmware: imx: adds miscdev pankaj.gupta
2026-09-16 13:16 ` Arnd Bergmann
2026-09-16 14:39 ` Frank Li
2026-10-05 14:28 ` Frieder Schrempf
2026-11-18 12:46 ` Frieder Schrempf
2026-11-18 14:43 ` Frieder Schrempf
2026-11-18 15:53 ` Frank Li
2026-11-18 16:01 ` Frieder Schrempf
2026-11-19 17:47 ` [EXT] " Pankaj Gupta
2026-11-19 18:49 ` Frieder Schrempf [this message]
2026-09-24 16:14 ` Pankaj Gupta
2026-09-14 19:40 ` [PATCH v51 6/7] arm64: dts: imx8ulp: add secure enclave node pankaj.gupta
2026-09-14 19:40 ` [PATCH v51 7/7] arm64: dts: imx8ulp: add reserved memory for EdgeLock Enclave pankaj.gupta
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=463b3707-4126-4f32-990e-e8f02d278695@kontron.de \
--to=frieder.schrempf@kontron.de \
--cc=arnd@arndb.de \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=frank.li@nxp.com \
--cc=frank.li@oss.nxp.com \
--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=pankaj.gupta@oss.nxp.com \
--cc=peng.fan@nxp.com \
--cc=rdunlap@infradead.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=skhan@linuxfoundation.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
all inboxes | Powered by JetHome®