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

[Kent Gibson <warthog618@gmail.com>]

On Fri, Sep 27, 2024 at 09:42:21AM +0200, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bartosz.golaszewski@linaro.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".
>

I have no opinions on sysfs changes.

> Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
> ---
> Story time:
>
> I decided to learn rust. I figured I'd best find me a project to work on
> that would involve some proper coding but wouldn't have much impact on
> anything important when I inevitably get it wrong the first few times.
>
> I decided to write a sysfs-to-libgpiod compatibility layer based on
> FUSE. Since Rust is hard, I started prototyping the thing in python
> first to at least have the logic nailed down before I tackle the rust
> part.
>

Something along these lines[1]?

Cheers,
Kent.

[1]https://dev.to/krjakbrjak/simulating-gpio-sysfs-interface-with-fuse-and-c-30ga