[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<170603222994.30461.12710346561077104850.git-patchwork-notify@kernel.org>
Date: Tue, 23 Jan 2024 17:50:29 +0000
From: patchwork-bot+linux-riscv@...nel.org
To: Vincent Chen <vincent.chen@...ive.com>
Cc: linux-riscv@...ts.infradead.org, daniel.lezcano@...aro.org,
tglx@...utronix.de, paul.walmsley@...ive.com, palmer@...belt.com,
aou@...s.berkeley.edu, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] clocksource: extend the max_delta_ns of timer-riscv and
timer-clint to ULONG_MAX
Hello:
This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@...osinc.com>:
On Tue, 5 Sep 2023 15:09:45 +0800 you wrote:
> When registering the riscv-timer or clint-timer as a clock_event device,
> the driver needs to specify the value of max_delta_ticks. This value
> directly influences the max_delta_ns, which represents the maximum time
> interval for configuring subsequent clock events. Currently, both
> riscv-timer and clint-timer are set with a max_delta_ticks value of
> 0x7fff_ffff. When the timer operates at a high frequency, this values
> limists the system to sleep only for a short time. For the 1GHz case,
> the sleep cannot exceed two seconds. To address this limitation, refer to
> other timer implementations to extend it to 2^(bit-width of the timer) - 1.
> Because the bit-width of $mtimecmp is 64bit, this value becomes ULONG_MAX
> (0xffff_ffff_ffff_ffff).
>
> [...]
Here is the summary with links:
- clocksource: extend the max_delta_ns of timer-riscv and timer-clint to ULONG_MAX
https://git.kernel.org/riscv/c/d38e2e7bcb3e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists