From: Cristian Marussi <cristian.marussi@arm.com>
To: Peng Fan <peng.fan@nxp.com>
Cc: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>,
"sudeep.holla@arm.com" <sudeep.holla@arm.com>,
"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Aisheng Dong <aisheng.dong@nxp.com>,
Nitin Garg <nitin.garg_3@nxp.com>,
Ranjani Vaidyanathan <ranjani.vaidyanathan@nxp.com>,
Ye Li <ye.li@nxp.com>
Subject: Re: [PATCH] pinctrl: scmi: support i.MX OEM pin configuration type
Date: Mon, 26 Feb 2024 15:17:08 +0000 [thread overview]
Message-ID: <ZdyrdOmtYH0paGIh@pluto> (raw)
In-Reply-To: <DU0PR04MB94172086AB4EF0389B78CA6A885A2@DU0PR04MB9417.eurprd04.prod.outlook.com>
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
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-02-26 15:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 7:15 [PATCH] pinctrl: scmi: support i.MX OEM pin configuration type Peng Fan (OSS)
2024-02-26 13:16 ` Peng Fan
2024-02-26 15:17 ` Cristian Marussi [this message]
2024-02-27 0:51 ` Peng Fan
2024-02-29 13:51 ` Linus Walleij
2024-03-14 2:01 ` Peng Fan
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=ZdyrdOmtYH0paGIh@pluto \
--to=cristian.marussi@arm.com \
--cc=aisheng.dong@nxp.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nitin.garg_3@nxp.com \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.com \
--cc=ranjani.vaidyanathan@nxp.com \
--cc=sudeep.holla@arm.com \
--cc=ye.li@nxp.com \
/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;
as well as URLs for NNTP newsgroup(s).