[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20240406111757.1597-4-jszhang@kernel.org>
Date: Sat, 6 Apr 2024 19:17:57 +0800
From: Jisheng Zhang <jszhang@...nel.org>
To: Daniel Lezcano <daniel.lezcano@...aro.org>,
Thomas Gleixner <tglx@...utronix.de>,
Paul Walmsley <paul.walmsley@...ive.com>,
Palmer Dabbelt <palmer@...belt.com>,
Albert Ou <aou@...s.berkeley.edu>,
Samuel Holland <samuel.holland@...ive.com>
Cc: linux-kernel@...r.kernel.org,
linux-riscv@...ts.infradead.org
Subject: [PATCH v2 3/3] clocksource/drivers/timer-clint: Add set_state_oneshot_stopped
To avoid spurious timer interrupts when KTIME_MAX is used, we need to
configure set_state_oneshot_stopped(). Although implementing this is
optional, it still affects things like power management for the extra
timer interrupt.
Check commit 8fff52fd5093 ("clockevents: Introduce
CLOCK_EVT_STATE_ONESHOT_STOPPED state") for more information.
Signed-off-by: Jisheng Zhang <jszhang@...nel.org>
---
drivers/clocksource/timer-clint.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/clocksource/timer-clint.c b/drivers/clocksource/timer-clint.c
index 1c17eff9861e..f468fa8bf5f0 100644
--- a/drivers/clocksource/timer-clint.c
+++ b/drivers/clocksource/timer-clint.c
@@ -134,6 +134,7 @@ static DEFINE_PER_CPU(struct clock_event_device, clint_clock_event) = {
.rating = 100,
.set_next_event = clint_clock_next_event,
.set_state_shutdown = clint_clock_shutdown,
+ .set_state_oneshot_stopped = clint_clock_shutdown,
};
static int clint_timer_starting_cpu(unsigned int cpu)
--
2.43.0
Powered by blists - more mailing lists