From: "enlin.mu" <enlin.mu@linux.dev>
To: mani@kernel.org, daniel.lezcano@linaro.org, tglx@linutronix.de,
linux-arm-kernel@lists.infradead.org,
linux-unisoc@lists.infradead.org, linux-kernel@vger.kernel.org,
enlin.mu@unisoc.com
Subject: Re: [PATCH V2] clocksource/drivers/rda: Add sched_clock_register for RDA8810PL SoC
Date: Mon, 17 Nov 2025 10:13:24 +0800 [thread overview]
Message-ID: <a292bf98-74e2-405c-bb7c-3686959cdb10@linux.dev> (raw)
In-Reply-To: <20251107063347.3692-1-enlin.mu@linux.dev>
Hi Everyone
Who can help review this patch?
thanks
On 2025/11/7 14:33, Enlin Mu wrote:
> From: Enlin Mu <enlin.mu@unisoc.com>
>
> The current system log timestamp accuracy is tick, which can not
> meet the usage requirements and needs to reach nanoseconds.
> Therefore, the sched_clock_register funciton needs to be add.
>
> Signed-off-by: Enlin Mu <enlin.mu@unisoc.com>
> ---
> drivers/clocksource/timer-rda.c | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/clocksource/timer-rda.c b/drivers/clocksource/timer-rda.c
> index fd1199c189bf..0be8e05970e2 100644
> --- a/drivers/clocksource/timer-rda.c
> +++ b/drivers/clocksource/timer-rda.c
> @@ -13,6 +13,7 @@
>
> #include <linux/init.h>
> #include <linux/interrupt.h>
> +#include <linux/sched_clock.h>
>
> #include "timer-of.h"
>
> @@ -153,7 +154,7 @@ static struct timer_of rda_ostimer_of = {
> },
> };
>
> -static u64 rda_hwtimer_read(struct clocksource *cs)
> +static u64 rda_hwtimer_clocksource_read(void)
> {
> void __iomem *base = timer_of_base(&rda_ostimer_of);
> u32 lo, hi;
> @@ -167,6 +168,11 @@ static u64 rda_hwtimer_read(struct clocksource *cs)
> return ((u64)hi << 32) | lo;
> }
>
> +static u64 rda_hwtimer_read(struct clocksource *cs)
> +{
> + return rda_hwtimer_clocksource_read();
> +}
> +
> static struct clocksource rda_hwtimer_clocksource = {
> .name = "rda-timer",
> .rating = 400,
> @@ -185,6 +191,7 @@ static int __init rda_timer_init(struct device_node *np)
> return ret;
>
> clocksource_register_hz(&rda_hwtimer_clocksource, rate);
> + sched_clock_register(rda_hwtimer_clocksource_read, 64, rate);
>
> clockevents_config_and_register(&rda_ostimer_of.clkevt, rate,
> 0x2, UINT_MAX);
next prev parent reply other threads:[~2025-11-17 2:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 6:33 [PATCH V2] clocksource/drivers/rda: Add sched_clock_register for RDA8810PL SoC Enlin Mu
2025-11-17 2:13 ` enlin.mu [this message]
2025-11-17 9:36 ` Manivannan Sadhasivam
2025-11-17 10:20 ` enlin.mu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a292bf98-74e2-405c-bb7c-3686959cdb10@linux.dev \
--to=enlin.mu@linux.dev \
--cc=daniel.lezcano@linaro.org \
--cc=enlin.mu@unisoc.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unisoc@lists.infradead.org \
--cc=mani@kernel.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).