[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250624102726.pzk3zc6hbrmete2g@lcpd911>
Date: Tue, 24 Jun 2025 15:57:26 +0530
From: Dhruva Gole <d-gole@...com>
To: Markus Schneider-Pargmann <msp@...libre.com>
CC: Daniel Lezcano <daniel.lezcano@...aro.org>,
Thomas Gleixner
<tglx@...utronix.de>,
Vishal Mahaveer <vishalm@...com>, Kevin Hilman
<khilman@...libre.com>,
Sebin Francis <sebin.francis@...com>,
Kendall Willis
<k-willis@...com>, Akashdeep Kaur <a-kaur@...com>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/3] clocksource/drivers/timer-ti-dm: Fix property name
in comment
On Jun 23, 2025 at 21:24:28 +0200, Markus Schneider-Pargmann wrote:
> ti,always-on property doesn't exist. ti,timer-alwon is meant here. Fix
> this minor bug in the comment.
>
> Signed-off-by: Markus Schneider-Pargmann <msp@...libre.com>
> ---
> drivers/clocksource/timer-ti-dm-systimer.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/clocksource/timer-ti-dm-systimer.c b/drivers/clocksource/timer-ti-dm-systimer.c
> index 985a6d08512b42f499b3e243eb69cc9674bc8e53..fb0a3cc23b5a35e2906a253d36ccef2baccca50a 100644
> --- a/drivers/clocksource/timer-ti-dm-systimer.c
> +++ b/drivers/clocksource/timer-ti-dm-systimer.c
> @@ -226,7 +226,7 @@ static bool __init dmtimer_is_preferred(struct device_node *np)
> * Some omap3 boards with unreliable oscillator must not use the counter_32k
> * or dmtimer1 with 32 KiHz source. Additionally, the boards with unreliable
> * oscillator should really set counter_32k as disabled, and delete dmtimer1
> - * ti,always-on property, but let's not count on it. For these quirky cases,
> + * ti,timer-alwon property, but let's not count on it. For these quirky cases,
Reviewed-by: Dhruva Gole <d-gole@...com>
--
Best regards,
Dhruva Gole
Texas Instruments Incorporated
Powered by blists - more mailing lists