linux-kernel - Re: [PATCH 2/2] dt-bindings: gpio: Add gpio-latch binding document

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20220901075328.GO24324@pengutronix.de>
Date:   Thu, 1 Sep 2022 09:53:28 +0200
From:   Sascha Hauer <s.hauer@...gutronix.de>
To:     Linus Walleij <linus.walleij@...aro.org>
Cc:     linux-gpio@...r.kernel.org, linux-kernel@...r.kernel.org,
        Bartosz Golaszewski <brgl@...ev.pl>, kernel@...gutronix.de
Subject: Re: [PATCH 2/2] dt-bindings: gpio: Add gpio-latch binding document

On Wed, Aug 31, 2022 at 02:40:13PM +0200, Linus Walleij wrote:
> On Mon, Aug 29, 2022 at 4:40 PM Sascha Hauer <s.hauer@...gutronix.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")

Fine with me.

Sascha

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |