Re: [PATCH] gpio: Do not trigger WARN() with sysfs gpio export/unexport

[Bartosz Golaszewski <brgl@xxxxxxxx>]

On Tue, Nov 10, 2020 at 3:31 PM Linus Walleij <linus.walleij@xxxxxxxxxx> wrote:
>
> On Fri, Nov 6, 2020 at 12:27 PM Damien Le Moal <Damien.LeMoal@xxxxxxx> wrote:
>
> > It may not be the best interface for regular end users to
> > manipulate gpios, but it is definitely super useful for developers to do quick
> > tests of their setup/drivers (which is what I did for my work with the Kendryte
> > K210 RISC-V SoC support).
>
> It is a bit discouraging that RISC-V, which was invented after we already
> obsoleted the sysfs ABI, is deploying this for development and test.
>
> We need to think about a similar facility for users which is less
> damaging but fulfils the same needs. I think I saw something a while
> back that looked promising and added some funky files in debugfs
> in a hierarchical manner per-gpiochip instead. That is how debugfs
> should be used.
>

Basically something like what gpio-mockup does for events? Was it
something out-of-tree or was it on the mailing list?

Also: quick tests have the tendency to become long-term solutions. :)

Is gpioget/gpioset duo difficult/cumbersome to use? It's a serious
question - I wrote it in a way that was as user-friendly as possible
but maybe I'm missing something about sysfs that makes users prefer it
over a command-line tool. To me sysfs was always a PITA with the
global numbers etc. but it still seems to stick with others.

Bartosz