[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0fc89d71-6510-4ca9-a789-290e1818798c@linaro.org>
Date: Tue, 29 Apr 2025 15:19:25 +0200
From: Daniel Lezcano <daniel.lezcano@...aro.org>
To: Jon Hunter <jonathanh@...dia.com>, Robert Lin <robelin@...dia.com>
Cc: thierry.reding@...il.com, tglx@...utronix.de, pohsuns@...dia.com,
linux-kernel@...r.kernel.org, linux-tegra@...r.kernel.org, sumitg@...dia.com
Subject: Re: [PATCH v5 1/3] clocksource/drivers/timer-tegra186: add
WDIOC_GETTIMELEFT support
On 29/04/2025 11:15, Jon Hunter wrote:
> Hi Daniel,
>
> On 29/04/2025 09:59, Daniel Lezcano wrote:
>> On Mon, Apr 21, 2025 at 06:08:19PM +0800, Robert Lin wrote:
>>> From: Pohsun Su <pohsuns@...dia.com>
>>>
>>> This change adds support for WDIOC_GETTIMELEFT so userspace
>>> programs can get the number of seconds before system reset by
>>> the watchdog timer via ioctl.
>>>
>>> Signed-off-by: Pohsun Su <pohsuns@...dia.com>
>>> Signed-off-by: Robert Lin <robelin@...dia.com>
>>> ---
>>
>> Hi Robert,
>>
>> I realize that this driver should be split in two and the watchdog
>> part go
>> under drivers/watchdog.
>
> Are there any other examples you know of where the timer is split in
> this way? It is not clear to me how you propose we do this?
Just keep the clocksource and move the watchdog code (everything related
to the watchdog_ops) to a new driver under drivers/watchdog
BTW, there are three clocksources with the same rating, what is the
point of having them supported ?
Is it not the architected clocksource enough ?
May be the clocksource can be removed and the driver remains a pure
watchdog driver ?
> BTW, for this series, I just want to get these updates merged. Any other
> re-factoring we can handle later.
>
> Cheers!
> Jon
>
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
Powered by blists - more mailing lists