From: Trent Piepho <firstname.lastname@example.org> To: Tony Lindgren <email@example.com> Cc: Drew Fustini <firstname.lastname@example.org>, Rob Herring <email@example.com>, Linus Walleij <firstname.lastname@example.org>, Jason Kridner <email@example.com>, Robert Nelson <firstname.lastname@example.org>, email@example.com, firstname.lastname@example.org, email@example.com, linux-gpio <firstname.lastname@example.org>, Christina Quast <email@example.com> Subject: Re: [PATCH] ARM: dts: document pinctrl-single,pins when #pinctrl-cells = 2 Date: Tue, 29 Sep 2020 13:15:45 -0700 Message-ID: <CA+7tXihBdw9AOGL7Hp2cH9+ii8fUXaaZZDUP3icyeOkMuGm4qA@mail.gmail.com> (raw) In-Reply-To: <20200924070443.GF9471@atomide.com> On Thu, Sep 24, 2020 at 12:04 AM Tony Lindgren <firstname.lastname@example.org> wrote: > > * Trent Piepho <email@example.com> [200924 06:31]: > > > > > > > > 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? > > Certainly different compatible strings can be used as needed. > But pinctrl-single is not going to be am335x specific though :) > We have quite a few SoCs using it: So what doesn't make sense to me, is to put something am335x specific like two cells for conf and mux, into a generic driver like pinctrl single. This series adds two cells ORed into one. Ok, that's generic, other platforms could use it. But it also accomplishes nothing, so what's the point? You've hinted there is more to come, which will accomplish something, but what is it? That can be: Used by platforms other than am335x Can't already be done with the pinctrl single pinconf features Needs more than one data cell per pin > > Are the driver changes something that can be not be done with the > > pinconf-single properties? They all include a mask. > > Sure but in the long term we're better off with using #pinctrl-cells > along the lines what we have for example for #interrupt-cells and > #gpio-cells. So if you look at gpio-cells, virtually every driver uses 2, where one cell is the gpio index and the other is a common set of flags. It's the standard layout of a gpio handle that almost all bindings use. Only a handful of platform specific gpio drivers have another cell to indicate bank (probably better to have made each bank its own device node). Interrupt controllers have different numbers of cells, but they are all platform specific, and the cells have defined platform specific meanings. pci-host-cam-generic is a somewhat generic interrupt controller and it uses 1 cell, since it lacks device specific fields to put into additional cells. So I don't see an example of multiple cells which do not have a defined meaning that applies to all devices using the bindings. Consider also that any future changes to the pinctrl-single bindings would need to be backward compatible with a device tree binary where two cells get combined. So if the bindings being added here aren't done, then adding them now creates an unnecessary additional version to deal with for backward compatibility.
next prev parent reply index Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-14 10:43 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 [this message] 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+7tXihBdw9AOGL7Hp2cH9+ii8fUXaaZZDUP3icyeOkMuGm4qA@mail.gmail.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.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
Linux-OMAP Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/linux-omap/0 linux-omap/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 linux-omap linux-omap/ https://lore.kernel.org/linux-omap \ firstname.lastname@example.org public-inbox-index linux-omap Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.kernel.vger.linux-omap AGPL code for this site: git clone https://public-inbox.org/public-inbox.git