[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdaqKJLUdf3NiFHaTgu6buyhMb_D1yKyHF4M=eTQ94pe-g@mail.gmail.com>
Date: Sun, 27 Jun 2021 13:36:18 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Dipen Patel <dipenp@...dia.com>
Cc: "thierry.reding@...il.com" <thierry.reding@...il.com>,
Jon Hunter <jonathanh@...dia.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
linux-tegra <linux-tegra@...r.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
Bartosz Golaszewski <bgolaszewski@...libre.com>,
Kent Gibson <warthog618@...il.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>,
Linux Doc Mailing List <linux-doc@...r.kernel.org>,
Rob Herring <robh+dt@...nel.org>
Subject: Re: [RFC 09/11] tools: gpio: Add new hardware clock type
On Sat, Jun 26, 2021 at 1:48 AM Dipen Patel <dipenp@...dia.com> wrote:
> gpiolib-cdev is extended to support hardware clock type, this
> patch reflects that fact.
>
> Signed-off-by: Dipen Patel <dipenp@...dia.com>
(...)
> case 'w':
> config.flags |= GPIO_V2_LINE_FLAG_EVENT_CLOCK_REALTIME;
> break;
> + case 't':
> + config.flags |= GPIO_V2_LINE_FLAG_EVENT_CLOCK_HARDWARE;
> + break;
After the checking of the command line options we need a small sanity
check so we don't try to enable both realtime and hardware clock
at the same time, we will only be able to request one of them.
Yours,
Linus Walleij
Powered by blists - more mailing lists