[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b87fa5d8-bef9-9046-9747-d4428ddf58ea@nvidia.com>
Date: Thu, 29 Jul 2021 20:17:22 -0700
From: Dipen Patel <dipenp@...dia.com>
To: Linus Walleij <linus.walleij@...aro.org>
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 6/27/21 4:36 AM, Linus Walleij wrote:
> 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.
This will any way fail at gpiolib-cdev layer. Do we want to add it here
as well?
>
> Yours,
> Linus Walleij
Powered by blists - more mailing lists