From: Frank Li <Frank.li@nxp.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: David Leonard <David.Leonard@digi.com>,
linux-arm-kernel@lists.infradead.org,
Dong Aisheng <aisheng.dong@nxp.com>,
Fabio Estevam <festevam@gmail.com>,
Shawn Guo <shawnguo@kernel.org>, Jacky Bai <ping.bai@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org
Subject: Re: [PATCH 4/6] pinctrl: ls1046a: Add pinctrl driver support
Date: Sat, 31 Aug 2024 12:14:35 -0400 [thread overview]
Message-ID: <ZtNBa4OZ1QO8WPlI@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <CACRpkdaiSX6zbyqUqKPwApS-zQ8KYMCqHs0F7Sx17jGN1bpJoQ@mail.gmail.com>
On Sat, Aug 31, 2024 at 12:26:47AM +0200, Linus Walleij wrote:
> On Tue, Aug 27, 2024 at 9:20 PM Frank Li <Frank.li@nxp.com> wrote:
> > On Tue, Aug 27, 2024 at 12:12:24PM +1000, David Leonard wrote:
> > >
> > > Add QorIQ LS1046A pinctrl driver allowing i2c-core to exert
> > > GPIO control over the third and fourth I2C buses.
> > >
> > > Signed-off-by: David Leonard <David.Leonard@digi.com>
> > > ---
> >
> > Why not use pinctrl-single, please ref fsl,lx2160x.dtsi for GPIO/i2c
> > recover.
>
> I'm not so sure about that. Since the 1012 need to use a unique
> driver this will be confusing across the family: one chip has
> registers and values defined in the device tree, another has
> them in the driver, if possible I would advice to keep this
> consistent across sibling SoCs.
There are not new productions of Layerscape. IMX will take over these.
There are only few I2C pins need mux to gpio. It is not wonth to add
new driver for it if pinctrl-single can work.
And 1012 pinctrl driver was not shared with 1046.
Frank
>
> I can't stop anyone from using pinctrl-single but it's a bit
> seductive in it's simplicity, while not always so user-friendly
> with all the magic that ends up in the device trees.
>
> Yours,
> Linus Walleij
next prev parent reply other threads:[~2024-08-31 16:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 2:12 David Leonard
2024-08-27 19:19 ` Frank Li
2024-08-30 22:26 ` Linus Walleij
2024-08-31 16:14 ` Frank Li [this message]
2024-08-27 21:10 ` kernel test robot
2024-08-27 21:31 ` kernel test robot
2024-08-28 7:16 ` kernel test robot
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=ZtNBa4OZ1QO8WPlI@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=David.Leonard@digi.com \
--cc=aisheng.dong@nxp.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--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=ping.bai@nxp.com \
--cc=shawnguo@kernel.org \
/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
all inboxes | Powered by JetHome®