From: Trent Piepho <tpiepho@gmail.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Drew Fustini <drew@beagleboard.org>,
Rob Herring <robh+dt@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Jason Kridner <jkridner@beagleboard.org>,
Robert Nelson <robertcnelson@gmail.com>,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org,
linux-gpio <linux-gpio@vger.kernel.org>,
Christina Quast <cquast@hanoverdisplays.com>
Subject: Re: [PATCH] ARM: dts: document pinctrl-single,pins when #pinctrl-cells = 2
Date: Wed, 23 Sep 2020 23:31:04 -0700 [thread overview]
Message-ID: <CA+7tXijkS8UMFk4t=DuKjZZNnThbRarPQvxwxjg-uJFTKJRsXA@mail.gmail.com> (raw)
In-Reply-To: <20200924060645.GD9471@atomide.com>
On Wed, Sep 23, 2020 at 11:06 PM Tony Lindgren <tony@atomide.com> wrote:
>
> * Trent Piepho <tpiepho@gmail.com> [200924 05:49]:
> > On Wed, Sep 23, 2020 at 10:43 PM Tony Lindgren <tony@atomide.com> wrote:
> > >
> > > * Trent Piepho <tpiepho@gmail.com> [200924 01:34]:
> > > > On Tue, Sep 22, 2020 at 11:57 PM Tony Lindgren <tony@atomide.com> wrote:
> > > > >
> > > > > Also FYI, folks have also complained for a long time that the pinctrl-single
> > > > > binding mixes mux and conf values while they should be handled separately.
> > > > >
> > > >
> > > > Instead of combining two fields when the dts is generated they are now
> > > > combined when the pinctrl-single driver reads the dts. Other than
> > > > this detail, the result is the same. The board dts source is the
> > > > same. The value programmed into the pinctrl register is the same.
> > > > There is no mechanism currently that can alter that value in any way.
> > > >
> > > > What does combining them later allow that is not possible now?
> > >
> > > It now allows further driver changes to manage conf and mux separately :)
> >
> > The pinctrl-single driver? How will that work with boards that are
> > not am335x and don't use conf and mux fields in the same manner as
> > am335x?
>
> For those cases we still have #pinctrl-cells = <1>.
If pincntrl-single is going to be am335x specific, then shouldn't it
be a different compatible string?
Are the driver changes something that can be not be done with the
pinconf-single properties? They all include a mask.
next prev parent reply other threads:[~2020-09-24 6:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 10:43 [PATCH] ARM: dts: document pinctrl-single,pins when #pinctrl-cells = 2 Drew Fustini
2020-09-17 9:03 ` Trent Piepho
2020-09-17 9:20 ` Drew Fustini
2020-09-17 10:00 ` Trent Piepho
2020-09-17 10:39 ` Drew Fustini
2020-09-23 6:57 ` Tony Lindgren
2020-09-24 1:34 ` Trent Piepho
2020-09-24 5:43 ` Tony Lindgren
2020-09-24 5:49 ` Trent Piepho
2020-09-24 6:06 ` Tony Lindgren
2020-09-24 6:31 ` Trent Piepho [this message]
2020-09-24 7:04 ` Tony Lindgren
2020-09-29 20:15 ` Trent Piepho
2020-09-30 5:15 ` Tony Lindgren
2020-09-30 8:34 ` Trent Piepho
2020-09-30 9:15 ` Tony Lindgren
2020-09-30 9:34 ` Trent Piepho
2020-09-30 9:47 ` Tony Lindgren
2020-09-30 18:50 ` Trent Piepho
2020-10-01 7:00 ` Tony Lindgren
2020-09-23 6:59 ` Tony Lindgren
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='CA+7tXijkS8UMFk4t=DuKjZZNnThbRarPQvxwxjg-uJFTKJRsXA@mail.gmail.com' \
--to=tpiepho@gmail.com \
--cc=cquast@hanoverdisplays.com \
--cc=devicetree@vger.kernel.org \
--cc=drew@beagleboard.org \
--cc=jkridner@beagleboard.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=robertcnelson@gmail.com \
--cc=robh+dt@kernel.org \
--cc=tony@atomide.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).