All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Andrew Geissler <geissonator@gmail.com>
Cc: openbmc <openbmc@lists.ozlabs.org>
Subject: Re: Proposed deprecation of device-tree-gpio-naming.md
Date: Thu, 07 Aug 2025 09:31:40 +0930	[thread overview]
Message-ID: <0dd7de8da1a33b6b0ba3b613cacadc399a15e156.camel@codeconstruct.com.au> (raw)
In-Reply-To: <CALLMt=rt8Ngv2sRKOeQ-Gm=cccaw-d3j0WahqBXyQydhqC15nQ@mail.gmail.com>

On Wed, 2025-08-06 at 14:21 -0500, Andrew Geissler wrote:
> On Tue, Aug 5, 2025 at 6:54 PM Andrew Jeffery
> <andrew@codeconstruct.com.au> wrote:
> > 
> > Hello,
> > 
> > In the comment thread at [1] I've proposed deprecating the directions
> > in device-tree-gpio-naming.md[2] for the purpose of describing GPIOs in
> > devicetrees. Devicetrees represent the hardware, and from experience
> > over time I think it's best that they reflect the information from the
> > schematics without influence from software implementation choices.
> 
> Yeah agree, it seemed like a good idea at the time but there has been a
> lot of friction with this design over time. I know some reviews have simply
> been abandoned due to the frustrations of coming up with an agreed to
> gpio name. And other reviews have taken an excessive amount of time
> to get through.
> 
> > However, perhaps it's still a reasonable set of suggestions for
> > consumption of pins with the translation from net names done by the
> > applications themselves?
> 
> If we all agree, I could do one final update to the doc stating it's
> been deprecated
> 

Thanks!

>  but feel free to use the existing recommendations
> when creating a new system if it makes sense. And another note
> indicating some OpenBMC repos may require some work to support
> a new GPIO name.

Sounds good to me.

Andrew


  reply	other threads:[~2025-08-07  0:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-05 23:54 Proposed deprecation of device-tree-gpio-naming.md Andrew Jeffery
2025-08-06 19:21 ` Andrew Geissler
2025-08-07  0:01   ` Andrew Jeffery [this message]
2025-08-12 21:14 ` Patrick Williams
2025-08-13  1:03   ` Andrew Jeffery

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=0dd7de8da1a33b6b0ba3b613cacadc399a15e156.camel@codeconstruct.com.au \
    --to=andrew@codeconstruct.com.au \
    --cc=geissonator@gmail.com \
    --cc=openbmc@lists.ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.