[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <3758bdc7-2eb3-4e42-845a-8ecb1103d4f1@prolan.hu>
Date: Wed, 26 Feb 2025 14:56:56 +0100
From: Csókás Bence <csokas.bence@...lan.hu>
To: Dipen Patel <dipenp@...dia.com>, <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?
Hi,
On 2025. 02. 19. 23:32, Dipen Patel wrote:
> 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.
Yes, I had the same impression. But since there was already a driver for
this block in the counter subsystem, it was easier to extend that to our
use case.
> Thanks,
> Best Regards,
> Dipen Patel
>
Bence
Powered by blists - more mailing lists