[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <8cfc6478-2aa1-b864-88c9-99fe3c09e179@nvidia.com>
Date: Fri, 22 Apr 2022 15:52:09 -0700
From: Dipen Patel <dipenp@...dia.com>
To: Linus Walleij <linus.walleij@...aro.org>, thierry.reding@...il.com
Cc: jonathanh@...dia.com, smangipudi@...dia.com,
linux-kernel@...r.kernel.org, linux-tegra@...r.kernel.org,
linux-gpio@...r.kernel.org, bgolaszewski@...libre.com,
warthog618@...il.com, devicetree@...r.kernel.org,
linux-doc@...r.kernel.org, robh+dt@...nel.org
Subject: Re: [PATCH v5 00/11] Intro to Hardware timestamping engine
Hi Linus,
Thanks for the feedback. I have just sent v6 version reflecting review comments in dt binding.
I have also added some init APIs in hte core and moved few codes around. It does not change
much from the consumer point of view.
On 4/19/22 3:46 PM, Linus Walleij wrote:
> On Tue, Mar 29, 2022 at 7:45 AM Dipen Patel <dipenp@...dia.com> wrote:
>
>> This patch series introduces new subsystem called hardware timestamping
>> engine (HTE). It offers functionality such as timestamping through hardware
>> means in realtime. The HTE subsystem centralizes HTE provider and consumers
>> where providers can register themselves and the consumers can request
>> interested entity which could be lines, GPIO, signals or buses. The
>> HTE subsystem provides timestamp in nano seconds, having said that the provider
>> need to convert the timestamp if its not in that unit. There was upstream
>> discussion about the HTE at
>> https://lore.kernel.org/lkml/4c46726d-fa35-1a95-4295-bca37c8b6fe3@nvidia.com/
> I like this.
>
> Can you put it in a public git and make it eligible for Stephen Rothwell to
> pull into linux-next and ask him to do so, as we intend to merge this for
> v5.19?
>
> Yours,
> Linus Walleij
Powered by blists - more mailing lists