[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <7b6505ca-6082-4644-be4d-6e1372c183b7@nvidia.com>
Date: Wed, 19 Feb 2025 14:32:56 -0800
From: Dipen Patel <dipenp@...dia.com>
To: Csókás Bence <csokas.bence@...lan.hu>,
linux-iio@...r.kernel.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
linux-arm-kernel@...ts.infradead.org, timestamp@...ts.linux.dev
Cc: William Breathitt Gray <wbg@...nel.org>,
Jonathan Cameron <jic23@...nel.org>, Lars-Peter Clausen <lars@...afoo.de>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [Q] Frequency & duty cycle measurement?
On 1/21/25 7:19 AM, Csókás Bence wrote:
> he hardware is capable of taking a snapshot of the timer value into another
> dedicated register pair (RA, RB) on the rising/falling edges, and a small
> `devmem`-based userspace utility was created as a working PoC
I am late to the party :) Seems above statement looks lot like what HTE
subsystem is doing. Right now, only userspace path is through the gpiolib
due to usage that time was limited to GPIOs. However, we can extend HTE to meet
this scenario.
Thanks,
Best Regards,
Dipen Patel
Powered by blists - more mailing lists