linux-kernel - Re: [PATCH 1/3] clocksource/drivers/timer-ti-dm: Fix property name in comment

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <7hqzz7oap2.fsf@baylibre.com>
Date: Wed, 25 Jun 2025 12:58:17 -0700
From: Kevin Hilman <khilman@...libre.com>
To: Markus Schneider-Pargmann <msp@...libre.com>, Daniel Lezcano
 <daniel.lezcano@...aro.org>, Thomas Gleixner <tglx@...utronix.de>
Cc: Vishal Mahaveer <vishalm@...com>, Dhruva Gole <d-gole@...com>, Sebin
 Francis <sebin.francis@...com>, Kendall Willis <k-willis@...com>,
 Akashdeep Kaur <a-kaur@...com>, linux-kernel@...r.kernel.org, Markus
 Schneider-Pargmann <msp@...libre.com>
Subject: Re: [PATCH 1/3] clocksource/drivers/timer-ti-dm: Fix property name
 in comment

Markus Schneider-Pargmann <msp@...libre.com> writes:

> 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>

Reviewed-by: Kevin Hilman <khilman@...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,
>   * we prefer using the always-on secure dmtimer12 with the internal 32 KiHz
>   * clock as the clocksource, and any available dmtimer as clockevent.
>   *
>
> -- 
> 2.49.0