linux-kernel - Re: [RFC PATCH] gpio: sysfs: make the sysfs export behavior consistent

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] [day] [month] [year] [list]

Message-ID: <CAMRc=McaakkZZ0BWeneG6PrNKPto+Wc4T4-GGiUUnEqrQrxnWA@mail.gmail.com>
Date: Wed, 2 Oct 2024 16:31:08 +0200
From: Bartosz Golaszewski <brgl@...ev.pl>
To: Linus Walleij <linus.walleij@...aro.org>
Cc: Kent Gibson <warthog618@...il.com>, linux-gpio@...r.kernel.org, 
	linux-kernel@...r.kernel.org, 
	Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
Subject: Re: [RFC PATCH] gpio: sysfs: make the sysfs export behavior consistent

On Wed, Oct 2, 2024 at 3:12 PM Linus Walleij <linus.walleij@...aro.org> wrote:
>
> On Fri, Sep 27, 2024 at 9:42 AM Bartosz Golaszewski <brgl@...ev.pl> wrote:
>
> > From: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
> >
> > For drivers or board files that set gpio_chip->names, the links to the
> > GPIO attribute group created on sysfs export will be named after the
> > line's name set in that array. For lines that are named using device
> > properties, the names pointer of the gpio_chip struct is never assigned
> > so they are exported as if they're not named.
> >
> > The ABI documentation does not mention the former behavior and given
> > that the majority of modern systems use device-tree, ACPI or other way
> > of passing GPIO names using device properties - bypassing gc->names -
> > it's better to make the behavior consistent by always exporting lines as
> > "gpioXYZ".
> >
> > Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
>
> I'm in favor of this.
> Reviewed-by: Linus Walleij <linus.walleij@...aro.org>
>

I take it this also applies to v2 and am picking it up instead of this one.

Bart

> > Story time:
>
> That's a good story :) Fun to see how you arrived at this.
>
> Yours,
> Linus Walleij