All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Dahl <post@lespocky.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/gpiod: add gpiod hardware handling daemon
Date: Sat, 20 Jun 2020 14:33:40 +0200	[thread overview]
Message-ID: <20200620123339.tf7zog3j7zsad7nj@falbala.internal.home.lespocky.de> (raw)
In-Reply-To: <CAAj6r7oxgNt5ATvMhVKVqSxRay5HkN5Y+O-0r+ce-Ksg=q3nDw@mail.gmail.com>

Hei hei,

On Fri, Jun 19, 2020 at 10:25:52PM +0200, Marc Chalain wrote:
> Le ven. 19 juin 2020 ? 21:39, Alexander Dahl <post@lespocky.de> a ?crit :
> > However, I defined my button in dts as key, not just as gpio, because
> > it is actually a key and linux has infrastructure for that.
> > Furthermore there are reliable userspace libraries to not reinvent the
> > wheel. I was able to build something around libevdev in two days.
> >
> This solution may be complicated when you use some buttons for an
> application,
> and just another button for a system feature. You have to manage several
> keyboards,
>  to name each one by udev (or mdev) to use the good one with each
> application.

No and no.

There's no keyboard involved, the keycode I used is not even assigned
to a key usually found on keyboards. The system has neither udev nor
mdev, the key is ready by just defining it in dts.

> A daemon on GPIO will never replace a keyboard. When you need several
> events
> key and a short time response, a keyboard is more powerful.
> The Daemon is useful for few events in the life of the system, and you
> don't want
> modify an application.

This is exactly my usecase, a tiny daemon doing basically nothing but
waiting for a button press once a year or so.

> > Besides: your gpiod uses the well known libgpiod, but is not part of
> > that project, right? That is a little puzzling, people will mix that
> > up.
> >
> Yes I'm sorry for the name. I wanted to use direct access to the
> /dev/gpiochip,
> and after I saw that libgpiod was a kernel.org project. I should change the
> name
> but it's the right name for its usage, and it uses libgpiod, then the
> daemon promotes
> the library. Another name would have been stupid.
> I will propose the daemon to the libgpiod developer, when I will be ready.

Looking forward to that. :-)

Greets
Alex

-- 
/"\ ASCII RIBBON | ?With the first link, the chain is forged. The first
\ / CAMPAIGN     | speech censured, the first thought forbidden, the
 X  AGAINST      | first freedom denied, chains us all irrevocably.?
/ \ HTML MAIL    | (Jean-Luc Picard, quoting Judge Aaron Satie)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20200620/4920bc97/attachment.asc>

  reply	other threads:[~2020-06-20 12:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-16 16:42 [Buildroot] [PATCH 1/1] package/gpiod: add gpiod hardware handling daemon mchalain
2020-06-17 20:38 ` Thomas Petazzoni
2020-06-19 15:37   ` Marc Chalain
2020-06-19 19:39     ` Alexander Dahl
2020-06-19 20:25       ` Marc Chalain
2020-06-20 12:33         ` Alexander Dahl [this message]
2020-06-20 17:29           ` Marc Chalain
2020-06-26 11:29 Marc Chalain
2022-01-08 16:07 ` Romain Naour

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=20200620123339.tf7zog3j7zsad7nj@falbala.internal.home.lespocky.de \
    --to=post@lespocky.de \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.