From: Tony Lindgren <tony@atomide.com>
To: Trent Piepho <tpiepho@gmail.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, 30 Sep 2020 12:15:26 +0300 [thread overview]
Message-ID: <20200930091526.GQ9471@atomide.com> (raw)
In-Reply-To: <CA+7tXig=3hbFXfmYMC5Hd1Zc2n-6uGXbMePPw_Cr4bOsyt7QQA@mail.gmail.com>
* Trent Piepho <tpiepho@gmail.com> [200930 08:35]:
> The closest thing would be the generic pin config type bindings, which
> go in the pinctrl driver's nodes, and look like this:
> &am335x_pinmux {
> pinctrl_yoyo_reset: yoyogrp {
> pins = "foo";
> function = "gpio";
> bias-pull-up;
> };
> };
There's a bit of a dtb size and boot time issue for adding properties
for each pin where that needs to be done for several hundred pins :)
> Is "some additional property for specifying generic conf flags"
> different from the existing pinctrl-single,bias-pullup, etc.
> properties? Because splitting the data cell into two parts doesn't
> make any difference to those.
So with an interrupt style binding with generic pinconf flags we can
leave out the parsing of multiple properties for each pin. Sure the
pin is only referenced by the controller like you pointed out but the
pinconf flags could be generic.
Regards,
Tony
next prev parent reply other threads:[~2020-09-30 9:15 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
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 [this message]
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=20200930091526.GQ9471@atomide.com \
--to=tony@atomide.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=tpiepho@gmail.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).