linux-kernel - Re: [PATCH v4 5/7] firmware: imx: Add i.MX95 SCMI LMM driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250415091016.GB10243@nxa18884-linux>
Date: Tue, 15 Apr 2025 17:10:16 +0800
From: Peng Fan <peng.fan@....nxp.com>
To: Sudeep Holla <sudeep.holla@....com>
Cc: Peng Fan <peng.fan@....com>,
	Cristian Marussi <cristian.marussi@....com>,
	Shawn Guo <shawnguo@...nel.org>,
	Sascha Hauer <s.hauer@...gutronix.de>,
	Pengutronix Kernel Team <kernel@...gutronix.de>,
	Fabio Estevam <festevam@...il.com>, Rob Herring <robh@...nel.org>,
	Krzysztof Kozlowski <krzk+dt@...nel.org>,
	Conor Dooley <conor+dt@...nel.org>,
	Dan Carpenter <dan.carpenter@...aro.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"arm-scmi@...r.kernel.org" <arm-scmi@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>,
	"imx@...ts.linux.dev" <imx@...ts.linux.dev>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>
Subject: Re: [PATCH v4 5/7] firmware: imx: Add i.MX95 SCMI LMM driver

On Mon, Apr 14, 2025 at 12:17:34PM +0100, Sudeep Holla wrote:
>On Mon, Apr 14, 2025 at 11:00:20AM +0000, Peng Fan wrote:
>> 
>> Oops, I just checked wrong Kconfig under drivers/firmware/arm_scmi/
>> vendors/imx
>> 
>> Build this for ARM32 i.MX is ok, I just think no need. So add
>> a ARM64 dependency.
>> 
>
>OK, I will drop the ARM64 dependency when applying. I also don't understand

Thanks for helping on this.

>the dependency on i.MX firmware LMM and CPU drivers in the scmi vendor
>protocol as the dependency should be other way around. But I see Arnd had
>fixed it so I will keep it as you have posted to keep them all aligned.
Not dig into much on this.
I just followed what Arnd did when I prepared the patchset to avoid
potential build issue as reported before.

Thanks,
Peng

>
>-- 
>Regards,
>Sudeep