[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240129163043.if5jj4kyacqfe2n5@bogus>
Date: Mon, 29 Jan 2024 16:30:43 +0000
From: Sudeep Holla <sudeep.holla@....com>
To: Peng Fan <peng.fan@....nxp.com>
Cc: Cristian Marussi <cristian.marussi@....com>,
Rob Herring <robh+dt@...nel.org>,
Sudeep Holla <sudeep.holla@....com>,
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>,
NXP Linux Team <linux-imx@....com>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org, linux-gpio@...r.kernel.org,
AKASHI Takahiro <takahiro.akashi@...aro.org>,
Peng Fan <peng.fan@....com>, Rob Herring <robh@...nel.org>
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.
--
Regards,
Sudeep
Powered by blists - more mailing lists