From: Linus Walleij <linus.walleij@linaro.org>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Bartosz Golaszewski <brgl@bgdev.pl>,
kernel@pengutronix.de
Subject: Re: [PATCH 2/2] dt-bindings: gpio: Add gpio-latch binding document
Date: Wed, 31 Aug 2022 14:40:13 +0200 [thread overview]
Message-ID: <CACRpkdbA3FR_sFrj9FTH3Ui8so-j654wm=5yTMUydZttsU_HMw@mail.gmail.com> (raw)
In-Reply-To: <20220829144032.GC24324@pengutronix.de>
On Mon, Aug 29, 2022 at 4:40 PM Sascha Hauer <s.hauer@pengutronix.de> wrote:
> > Hm I wanted to just call these "gpios" but that is maybe confusing.
> > What about "latch-gpios"?
>
> Hm, the clk input is used to latch the current state of the inputs to
> the outputs, so "latch-gpios" might even be confused with the GPIO
> routed to the clk unput of the latch. Overall, the whole thing is a
> latch, so "latch-gpios" doesn't sound like a good name to distinguish
> the different types of inputs of a latch. I still like data-gpios best
> as these lines are described as "Data inputs" in my 74273 data sheet.
How about "latched-gpios" (notice the "d")
It makes some semantic sense.
But I will not nitpick, data is fine, just a bit unspecific.
Yours,
Linus Walleij
next prev parent reply other threads:[~2022-08-31 12:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 9:41 [PATCH 0/2] gpio: Add gpio-latch driver Sascha Hauer
2022-08-25 9:41 ` [PATCH 1/2] gpio: Add gpio latch driver Sascha Hauer
2022-08-26 5:53 ` Marco Felsch
2022-08-29 14:21 ` Sascha Hauer
2022-08-26 13:41 ` Linus Walleij
2022-08-25 9:41 ` [PATCH 2/2] dt-bindings: gpio: Add gpio-latch binding document Sascha Hauer
2022-08-26 13:37 ` Linus Walleij
2022-08-29 14:40 ` Sascha Hauer
2022-08-31 12:40 ` Linus Walleij [this message]
2022-09-01 7:53 ` Sascha Hauer
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='CACRpkdbA3FR_sFrj9FTH3Ui8so-j654wm=5yTMUydZttsU_HMw@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=brgl@bgdev.pl \
--cc=kernel@pengutronix.de \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
/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).