From: Arnd Bergmann <arnd@arndb.de>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Clemens Gruber <clemens.gruber@pqgruber.com>,
Thierry Reding <thierry.reding@gmail.com>,
Peter Rosin <peda@axentia.se>,
Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [RFC] libgpiod public API reviews needed
Date: Sun, 21 Jan 2018 23:18:59 +0100 [thread overview]
Message-ID: <CAK8P3a1JeOREOXWz+BBurs3odtDTGEUnpotbLEZEOsX7YUNfeA@mail.gmail.com> (raw)
In-Reply-To: <CAMRc=MdgntKcwO9ub3XOT6=hFaTZj_rT9O0SpWv=ANm4xRpttw@mail.gmail.com>
On Sun, Jan 21, 2018 at 10:30 PM, Bartosz Golaszewski <brgl@bgdev.pl> wrote:
> 2018-01-21 16:49 GMT+01:00 Linus Walleij <linus.walleij@linaro.org>:
>> On Fri, Jan 19, 2018 at 2:28 PM, Bartosz Golaszewski <brgl@bgdev.pl> wrote:
> I was not aware of this, but it seems you're right! Nice catch, thanks.
>
> How about defining a local struct gpiod_timespec with both seconds and
> nanoseconds explicitly defined to uint64_t?
Where is that timestamp generated? Is this purely a user space interface
with the time read from gettimeofday(), or are we talking about a new
kernel-to-user interface?
In a lot of cases, a simple 64-bit nanosecond counter using CLOCK_MONOTONIC
timestamps is the most robust and simple solution.
Arnd
next prev parent reply other threads:[~2018-01-21 22:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-19 13:28 [RFC] libgpiod public API reviews needed Bartosz Golaszewski
2018-01-20 16:02 ` Clemens Gruber
2018-01-21 21:14 ` Bartosz Golaszewski
2018-01-21 15:49 ` Linus Walleij
2018-01-21 21:30 ` Bartosz Golaszewski
2018-01-21 22:18 ` Arnd Bergmann [this message]
2018-01-22 8:21 ` Linus Walleij
2018-01-22 9:25 ` Arnd Bergmann
2018-01-22 9:28 ` Arnd Bergmann
2018-01-22 11:02 ` Bartosz Golaszewski
2018-01-22 11:12 ` Arnd Bergmann
2018-01-23 15:14 ` Bartosz Golaszewski
2018-01-22 12:02 ` Linus Walleij
2018-01-22 13:46 ` Arnd Bergmann
2018-01-23 14:15 ` Ludovic Desroches
2018-01-23 15:05 ` Bartosz Golaszewski
2018-01-25 16:29 ` Bartosz Golaszewski
2018-01-26 7:35 ` Ludovic Desroches
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=CAK8P3a1JeOREOXWz+BBurs3odtDTGEUnpotbLEZEOsX7YUNfeA@mail.gmail.com \
--to=arnd@arndb.de \
--cc=andy.shevchenko@gmail.com \
--cc=brgl@bgdev.pl \
--cc=clemens.gruber@pqgruber.com \
--cc=lars@metafoo.de \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=peda@axentia.se \
--cc=thierry.reding@gmail.com \
/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).