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 for Android: free password hash cracker in your pocket

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

Message-ID: <CACRpkdbA3FR_sFrj9FTH3Ui8so-j654wm=5yTMUydZttsU_HMw@mail.gmail.com>
Date:   Wed, 31 Aug 2022 14:40:13 +0200
From:   Linus Walleij <linus.walleij@...aro.org>
To:     Sascha Hauer <s.hauer@...gutronix.de>
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 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")

It makes some semantic sense.

But I will not nitpick, data is fine, just a bit unspecific.

Yours,
Linus Walleij