linux-gpio.vger.kernel.org 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: Re: [libgpiod v2][PATCH v3 4/5] tools: add gpiowatch
Date: Tue, 8 Nov 2022 23:38:43 +0800	[thread overview]
Message-ID: <Y2p4A6FM9nF5RLqw@sol> (raw)
In-Reply-To: <CAMRc=MdC9fcrKaXRTq5eQttdyLo_SwhU7qEeV9+ej3L0ENkrTA@mail.gmail.com>

On Tue, Nov 08, 2022 at 04:00:08PM +0100, Bartosz Golaszewski wrote:
> On Tue, Oct 11, 2022 at 2:29 AM Kent Gibson <warthog618@gmail.com> wrote:
> >
> > Add a gpiowatch tool, based on gpiomon, to report line info change
> > events read from chip file descriptors.
> >
> > Inspired by the gpio-watch tool in the linux kernel, but with gpiomon
> > features such as custom formatted output, filtering events of
> > interest and exiting after a number of events, so more useful for
> > scripting.
> >
> > Default output is minimalist, so just time, event type and line id.
> > Full event details are available using the custom formatted output.
> >
> > Signed-off-by: Kent Gibson <warthog618@gmail.com>
> > ---
> >
> > Changes v2 -> v3:
> >    - Minimise the default output to more closely match gpiomon.
> >    - Add --format option for when more detail is required.
> >    - Add --num-events option to exit after a number of events.
> >    - Add --event option to report only specific event types.
> >    - Add --quiet option to not print events.
> >    - fix monotonic to realtime conversion on 32 bit platforms.
> >
> 
> Nice and clean, I don't have any issues other than the regular
> coding-style bikeshedding.
> 

Will be renamed to gpionotify for v5, ok?

> What happened to the idea we've been floating about creating a single,
> busyboxy executable with links rather than separate executables? Have
> we ever agreed on it?
> 

Yeah, last we spoke on it we agreed it was of dubious value and a low
priority, so I didn't go anywhere with it.  You've reconsidered?

Cheers,
Kent.


  reply	other threads:[~2022-11-08 15:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-11  0:29 [libgpiod v2][PATCH v3 0/5] tools: improvements for v2 Kent Gibson
2022-10-11  0:29 ` [libgpiod v2][PATCH v3 1/5] tools: remove old code to simplify review Kent Gibson
2022-10-11  0:29 ` [libgpiod v2][PATCH v3 2/5] tools: line name focussed rework Kent Gibson
2022-11-08 13:13   ` Bartosz Golaszewski
2022-11-08 15:33     ` Kent Gibson
2022-11-08 18:25       ` Bartosz Golaszewski
2022-11-09  2:00         ` Kent Gibson
2022-11-09 11:16           ` Bartosz Golaszewski
2022-11-09 11:40             ` Kent Gibson
2022-10-11  0:29 ` [libgpiod v2][PATCH v3 3/5] tools: tests for " Kent Gibson
2022-10-11  0:29 ` [libgpiod v2][PATCH v3 4/5] tools: add gpiowatch Kent Gibson
2022-11-08 15:00   ` Bartosz Golaszewski
2022-11-08 15:38     ` Kent Gibson [this message]
2022-11-08 18:04       ` Bartosz Golaszewski
2022-11-09  1:57         ` Kent Gibson
2022-10-11  0:29 ` [libgpiod v2][PATCH v3 5/5] tools: gpiowatch tests 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=Y2p4A6FM9nF5RLqw@sol \
    --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 NNTP newsgroup(s).