devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: devicetree@vger.kernel.org
Subject: Re: gpio-line-names policy
Date: Wed, 8 Feb 2023 11:45:58 -0500	[thread overview]
Message-ID: <20230208164557.GA33531@localhost> (raw)
In-Reply-To: <CACRpkdYZ3C3a4x4HKr2-3+8-DM=PmObMAOdLDs4Wu5Cx1HWtsg@mail.gmail.com>

Hi Linus,

On Wed 2023-02-08 @ 04:01:05 PM, Linus Walleij wrote:
> On Tue, Feb 7, 2023 at 4:07 PM Trevor Woerner <twoerner@gmail.com> wrote:
> > But what about those lines that go out to general purpose headers such as
> > the 40 pins of the Raspberry Pi header? Most SBCs have some set of header
> > that's available to users to connect whatever devices they wish, many of
> > them have adopted the rpi's 40-pin layout.
> 
> I think using the names on the header is fine, what I didn't want to see
> is things like the name of the pin on the SoC package or names made
> up from kernel-internal software constructs. As long as it is something
> real, and preferably unique I'm fine with it.
> 
> One early example is the HiKey N96 board:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm64/boot/dts/hisilicon/hi3670-hikey970.dts

Thank you for the clarification. Thinking from the user's point of view, I
added the actual pin number, then the SoC name, then the pin's label.

https://lore.kernel.org/linux-riscv/20230208014504.18899-1-twoerner@gmail.com/T/#u

I'll send a v2 with just the pin's label. Would leaving the pin number, in
addition to the name, be okay?

Best regards,
	Trevor

  reply	other threads:[~2023-02-08 16:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-07 15:07 gpio-line-names policy Trevor Woerner
2023-02-08 15:01 ` Linus Walleij
2023-02-08 16:45   ` Trevor Woerner [this message]
2023-02-09 10:39     ` Linus Walleij

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=20230208164557.GA33531@localhost \
    --to=twoerner@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linus.walleij@linaro.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;
as well as URLs for NNTP newsgroup(s).