Linux-GPIO Archive mirror
 help / color / mirror / Atom feed
From: Kent Gibson <warthog618@gmail.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: linux-gpio@vger.kernel.org
Subject: [libgpiod][RFC] helper functions for basic use cases
Date: Tue, 7 May 2024 10:21:06 +0800	[thread overview]
Message-ID: <20240507022106.GC26136@rigel> (raw)

Hi Bart,

I realise you want to keep libgpiod minimal, but in my latest survey of the
problems that new or potential users are finding with libgpiod the most
common one was that it is way too complicated to do simple things.
They just want to request an input or output line and play with it.
They think that should be an easy thing to do, and will completely write
off libgpiod because it is not - the learning curve is too steep.
And they have a point.

I've raised this before, but I think libgpiod is in need of a small (and I
emphasize small) set of helper functions to simplify basic use cases,
like just requesting a single input or output line.  Maybe functions to
control setting bias, edge detection and debounce on inputs (using
reconfigure after the initial request).
The functions would be separated from the existing functions by naming,
e.g. gpiod_helper_XXX, or some such, so there would be no confusion with
the existing.

Any chance your position has changed since last I asked?

Cheers,
Kent.

             reply	other threads:[~2024-05-07  2:21 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-07  2:21 Kent Gibson [this message]
2024-05-10 18:37 ` [libgpiod][RFC] helper functions for basic use cases Bartosz Golaszewski
2024-05-11  1:11   ` Kent Gibson
2024-05-13  8:28     ` Bartosz Golaszewski
2024-05-13 10:13       ` Kent Gibson
2024-05-14 13:31         ` Bartosz Golaszewski
2024-05-14 13:38           ` Kent Gibson
2024-05-15  8:26             ` Bartosz Golaszewski
2024-05-15  9:18               ` Kent Gibson
2024-05-15 13:37                 ` Kent Gibson
2024-05-15 13:54                 ` Bartosz Golaszewski
2024-05-15 14:14                   ` Kent Gibson
2024-05-16  0:19                     ` Kent Gibson
2024-05-16 13:55                     ` Kent Gibson
2024-05-17 10:53                     ` Bartosz Golaszewski
2024-05-17 12:37                       ` Kent Gibson
2024-05-22 10:59                         ` Bartosz Golaszewski
2024-05-22 12:41                           ` Kent Gibson
2024-05-24 14:20                             ` Bartosz Golaszewski
2024-05-15  7:06       ` Martin Hundebøll
2024-05-15  9:32         ` Kent Gibson

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=20240507022106.GC26136@rigel \
    --to=warthog618@gmail.com \
    --cc=brgl@bgdev.pl \
    --cc=linux-gpio@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 read-only IMAP folder(s) and NNTP newsgroup(s).