From: Kent Gibson <warthog618@gmail.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: "Linus Walleij" <linus.walleij@linaro.org>,
"Gunnar Thörnqvist" <gunnar@igl.se>,
linux-gpio@vger.kernel.org,
"Bartosz Golaszewski" <bartosz.golaszewski@linaro.org>
Subject: Re: [libgpiod][PATCH v2 2/4] tools: use ppoll() where higher timeout resolution makes sense
Date: Wed, 17 Apr 2024 15:23:50 +0800 [thread overview]
Message-ID: <20240417072350.GA120983@rigel> (raw)
In-Reply-To: <20240416215222.175166-3-brgl@bgdev.pl>
On Tue, Apr 16, 2024 at 11:52:20PM +0200, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
>
> We allow timeout units to be specified in microseconds but for poll() we
> need to round them up to milliseconds. Switch to ppoll() to avoid losing
> precision.
>
> Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
> ---
> tools/gpiomon.c | 12 ++++++++++--
> tools/gpionotify.c | 12 ++++++++++--
> 2 files changed, 20 insertions(+), 4 deletions(-)
>
> diff --git a/tools/gpiomon.c b/tools/gpiomon.c
> index 40e6ac2..728a671 100644
> --- a/tools/gpiomon.c
> +++ b/tools/gpiomon.c
> @@ -176,7 +176,7 @@ static int parse_config(int argc, char **argv, struct config *cfg)
> cfg->fmt = optarg;
> break;
> case 'i':
> - cfg->idle_timeout = parse_period_or_die(optarg) / 1000;
> + cfg->idle_timeout = parse_period_or_die(optarg);
> break;
> case 'l':
> cfg->active_low = true;
> @@ -362,6 +362,7 @@ int main(int argc, char **argv)
> int num_lines, events_done = 0;
> struct gpiod_edge_event *event;
> struct line_resolver *resolver;
> + struct timespec idle_timeout;
> struct gpiod_chip *chip;
> struct pollfd *pollfds;
> unsigned int *offsets;
> @@ -453,7 +454,14 @@ int main(int argc, char **argv)
> for (;;) {
> fflush(stdout);
>
> - ret = poll(pollfds, resolver->num_chips, cfg.idle_timeout);
> + if (cfg.idle_timeout > 0) {
> + idle_timeout.tv_sec = cfg.idle_timeout / 1000000;
> + idle_timeout.tv_nsec =
> + (cfg.idle_timeout % 1000000) * 1000;
> + }
> +
> + ret = ppoll(pollfds, resolver->num_chips,
> + cfg.idle_timeout > 0 ? &idle_timeout : NULL, NULL);
> if (ret < 0)
> die_perror("error polling for events");
>
One minor nit - I would introduce a timespec pointer initialised to NULL
and set to point to idle_timeout within the if rather than repeat the
cfg.idle_timeout > 0 test.
But that is just personal preference, so either way,
Reviewed-by: Kent Gibson <warthog618@gmail.com>
for the series.
Cheers,
Kent.
> diff --git a/tools/gpionotify.c b/tools/gpionotify.c
> index d2aee15..962896c 100644
> --- a/tools/gpionotify.c
> +++ b/tools/gpionotify.c
> @@ -132,7 +132,7 @@ static int parse_config(int argc, char **argv, struct config *cfg)
> cfg->fmt = optarg;
> break;
> case 'i':
> - cfg->idle_timeout = parse_period_or_die(optarg) / 1000;
> + cfg->idle_timeout = parse_period_or_die(optarg);
> break;
> case 'n':
> cfg->events_wanted = parse_uint_or_die(optarg);
> @@ -374,6 +374,7 @@ int main(int argc, char **argv)
> int i, j, ret, events_done = 0, evtype;
> struct line_resolver *resolver;
> struct gpiod_info_event *event;
> + struct timespec idle_timeout;
> struct gpiod_chip **chips;
> struct gpiod_chip *chip;
> struct pollfd *pollfds;
> @@ -422,7 +423,14 @@ int main(int argc, char **argv)
> for (;;) {
> fflush(stdout);
>
> - ret = poll(pollfds, resolver->num_chips, cfg.idle_timeout);
> + if (cfg.idle_timeout > 0) {
> + idle_timeout.tv_sec = cfg.idle_timeout / 1000000;
> + idle_timeout.tv_nsec =
> + (cfg.idle_timeout % 1000000) * 1000;
> + }
> +
> + ret = ppoll(pollfds, resolver->num_chips,
> + cfg.idle_timeout > 0 ? &idle_timeout : NULL, NULL);
> if (ret < 0)
> die_perror("error polling for events");
>
> --
> 2.40.1
>
next prev parent reply other threads:[~2024-04-17 7:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 21:52 [libgpiod][PATCH v2 0/4] tools: timeout handling improvements Bartosz Golaszewski
2024-04-16 21:52 ` [libgpiod][PATCH v2 1/4] tools: rename timeout to idle_timeout in gpiomon and gpionotify Bartosz Golaszewski
2024-04-16 21:52 ` [libgpiod][PATCH v2 2/4] tools: use ppoll() where higher timeout resolution makes sense Bartosz Golaszewski
2024-04-17 7:23 ` Kent Gibson [this message]
2024-04-22 18:15 ` Bartosz Golaszewski
2024-04-22 23:31 ` Kent Gibson
2024-04-16 21:52 ` [libgpiod][PATCH v2 3/4] tools: allow longer time periods Bartosz Golaszewski
2024-04-16 21:52 ` [libgpiod][PATCH v2 4/4] tools: add minutes as a new supported time unit 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=20240417072350.GA120983@rigel \
--to=warthog618@gmail.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=gunnar@igl.se \
--cc=linus.walleij@linaro.org \
--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).