linux-kernel - RE: [PATCH v3 0/6] firmware: arm_scmi: Add SCMI v3.2 pincontrol protocol basic support

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 for Android: free password hash cracker in your pocket

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

Date: Thu, 1 Feb 2024 08:07:51 +0000
From: Peng Fan <peng.fan@....com>
To: Sudeep Holla <sudeep.holla@....com>, "Peng Fan (OSS)"
	<peng.fan@....nxp.com>, "cristian.marussi@....com" <cristian.marussi@....com>
CC: Cristian Marussi <cristian.marussi@....com>, Rob Herring
	<robh+dt@...nel.org>, Krzysztof Kozlowski
	<krzysztof.kozlowski+dt@...aro.org>, Conor Dooley <conor+dt@...nel.org>,
	Oleksii Moisieiev <oleksii_moisieiev@...m.com>, Linus Walleij
	<linus.walleij@...aro.org>, Shawn Guo <shawnguo@...nel.org>, Sascha Hauer
	<s.hauer@...gutronix.de>, Pengutronix Kernel Team <kernel@...gutronix.de>,
	Fabio Estevam <festevam@...il.com>, dl-linux-imx <linux-imx@....com>,
	"linux-arm-kernel@...ts.infradead.org"
	<linux-arm-kernel@...ts.infradead.org>, "linux-kernel@...r.kernel.org"
	<linux-kernel@...r.kernel.org>, "devicetree@...r.kernel.org"
	<devicetree@...r.kernel.org>, "linux-gpio@...r.kernel.org"
	<linux-gpio@...r.kernel.org>, AKASHI Takahiro <takahiro.akashi@...aro.org>,
	Rob Herring <robh@...nel.org>
Subject: RE: [PATCH v3 0/6] firmware: arm_scmi: Add SCMI v3.2 pincontrol
 protocol basic support

> Subject: Re: [PATCH v3 0/6] firmware: arm_scmi: Add SCMI v3.2 pincontrol
> protocol basic support
> 
> On Mon, Jan 29, 2024 at 08:36:50PM +0800, Peng Fan wrote:
> > Hi Sudeep, Cristian
> >
> > Would you pick up patch 1-4?
> 
> I will for v6.9 sometime.
> 
> > And for i.MX95 OEM extenstion, do you have any suggestions?
> > I have two points:
> > 1. use vendor compatible. This would also benefit when supporting
> > vendor protocol.
> 
> May be, but that was never on plate for standard protocols. So I don't like
> that approach either.
> 
> > 2. Introduce a property saying supporting-generic-pinconf
> >
> 
> I am not sure what you mean by that. But that doesn't sound right especial in
> context of SCMI. So I would say no.
> 
> > How do you think?
> >
> 
> I don't have any other suggestions than fix your driver to use the pinmux
> properly with features in the upstream pinmux subsystem.

So for OEM specific units in Pin Configuration Type and Enumerations,
Any ideas how to support them if not talking about i.MX?

Thanks,
Peng.

> 
> --
> Regards,
> Sudeep