| Message ID | 20220329054521.14420-1-dipenp@nvidia.com |
|---|---|
| Headers | show |
| Series | Intro to Hardware timestamping engine | expand |
On Tue, Mar 29, 2022 at 7:45 AM Dipen Patel <dipenp@nvidia.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
On Wed, Apr 20, 2022 at 12:46:43AM +0200, Linus Walleij wrote: > On Tue, Mar 29, 2022 at 7:45 AM Dipen Patel <dipenp@nvidia.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? Do you intend to maintain this as part of the pinctrl or GPIO trees with Dipen as a sub-maintainer? Or would you prefer for this to be a separate tree? Thierry
On Wed, Apr 20, 2022 at 3:47 PM Thierry Reding <thierry.reding@gmail.com> wrote: > On Wed, Apr 20, 2022 at 12:46:43AM +0200, Linus Walleij wrote: > > On Tue, Mar 29, 2022 at 7:45 AM Dipen Patel <dipenp@nvidia.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? > > Do you intend to maintain this as part of the pinctrl or GPIO trees with > Dipen as a sub-maintainer? Or would you prefer for this to be a separate > tree? It has nothing to do with pin control but a bit to do with GPIO and IIO. I think it needs to be its own tree just like regulators or clocks. Yours, Linus Walleij
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@nvidia.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