[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZdyrdOmtYH0paGIh@pluto>
Date: Mon, 26 Feb 2024 15:17:08 +0000
From: Cristian Marussi <cristian.marussi@....com>
To: Peng Fan <peng.fan@....com>
Cc: "Peng Fan (OSS)" <peng.fan@....nxp.com>,
"sudeep.holla@....com" <sudeep.holla@....com>,
"linus.walleij@...aro.org" <linus.walleij@...aro.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
Aisheng Dong <aisheng.dong@....com>,
Nitin Garg <nitin.garg_3@....com>,
Ranjani Vaidyanathan <ranjani.vaidyanathan@....com>,
Ye Li <ye.li@....com>
Subject: Re: [PATCH] pinctrl: scmi: support i.MX OEM pin configuration type
On Mon, Feb 26, 2024 at 01:16:51PM +0000, Peng Fan wrote:
> Hi Linus, Sudeep, Cristian,
>
> > Subject: [PATCH] pinctrl: scmi: support i.MX OEM pin configuration type
>
> Sorry to ping early, but this impacts the design and i.MX95 SoC upstream(
> although I removed pinctrl to let uboot init pinmux as of now), so I would
> like see whether are you ok with the approach or not. This is the best as
> of now I could think out to not adding more size to firmware and make the
> dts format similar as previous i.MX.
>
I'll let Linus and Sudeep argument better, but, for my understanding,
does this solve all the issue with supporting custom iMX DT pinctrl
bindings on top of the current SCMI pinctrl generic driver without the
need of your last 2 downstream patches, or I am missing somethimg?
Thanks,
Cristian
Powered by blists - more mailing lists