Re: [libgpiod][PATCH 2/2] tools: allow longer time periods

[Bartosz Golaszewski <brgl@xxxxxxxx>]

On Wed, Apr 10, 2024 at 1:37 AM Kent Gibson <warthog618@xxxxxxxxx> wrote:
>
> On Tue, Apr 09, 2024 at 07:24:43PM +0200, Bartosz Golaszewski wrote:
> > On Tue, Apr 9, 2024 at 6:05 PM Kent Gibson <warthog618@xxxxxxxxx> wrote:
> > >
> > > On Tue, Apr 09, 2024 at 04:58:52PM +0200, Gunnar Thörnqvist wrote:
> > > > Hi, Got a use case where a hold period is measured in more than seconds?
> > > > Specifically for a get.:::
> > > >
> > > > I can see a large number of use cases where the time can be hours, days and
> > > > weeks. In my case, pin 17 controls a relay that heats water when electricity
> > > > is cheapest. It is ok to only have seconds as unit but the range must be
> > > > larger. /Gunnar
> > > >
> > >
> > > I was asking specifically about the case for gpioget, where a long hold
> > > period makes absolutely no sense.
> > >
> >
> > One could argue that this option doesn't make sense at all for gpioget. :)
> >
>
> And one would be wrong.  The point of the hold period for gets is to
> allow the line to settle after a config change before the get itself is
> performed.
>

One is indeed wrong.

> > I don't think it hurts to support a longer period of time even if only
> > for code reuse and less surface for bugs.
> >
>
> Well that is a complicated bit of code.
>

I'll submit the daemon RFC tomorrow or on Friday. Maybe this change
isn't even needed after all.

Bart

> Cheers,
> Kent.