From: Kent Gibson <warthog618@gmail.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [RFC PATCH] gpio: sysfs: make the sysfs export behavior consistent
Date: Mon, 30 Sep 2024 15:55:43 +0800 [thread overview]
Message-ID: <20240930075543.GB57004@rigel> (raw)
In-Reply-To: <CAMRc=Mdt8+ATGVU19E+pRrMhKZTcO49HTPdboHLLeN_Omd6LoQ@mail.gmail.com>
On Mon, Sep 30, 2024 at 09:20:48AM +0200, Bartosz Golaszewski wrote:
> On Mon, Sep 30, 2024 at 3:03 AM Kent Gibson <warthog618@gmail.com> wrote:
> >
> > > 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
> >
>
> Well, this doesn't really do anything. I'm thinking about something
> consuming the libgpiod rust bindings to actually be a useful
> replacement for kernel sysfs.
>
I haven't actually looked at that - but when you mentioned a sysfs fuse
interface that rang a bell.
> The master plan is: provide a drop-in user-space replacement for
> sysfs, make users convert to using it instead of the real thing,
> eventually remove sysfs from the kernel and then some time after
> remove the compatibility layer from existence forcing everybody to now
> move to pure libgpiod. :)
>
Ironically a lot of users would probably be happier with that than with
the D-bus daemon. And for that reason I don't think that last step will
ever happen. But that is ok too - as long as we can finally remove the
sysfs interface from the kernel.
Cheers,
Kent.
next prev parent reply other threads:[~2024-09-30 7:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-27 7:42 [RFC PATCH] gpio: sysfs: make the sysfs export behavior consistent Bartosz Golaszewski
2024-09-30 1:03 ` Kent Gibson
2024-09-30 7:20 ` Bartosz Golaszewski
2024-09-30 7:55 ` Kent Gibson [this message]
2024-10-02 13:12 ` Linus Walleij
2024-10-02 14:31 ` Bartosz Golaszewski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240930075543.GB57004@rigel \
--to=warthog618@gmail.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).