From: tomasz.figa@gmail.com (Tomasz Figa)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: exynos: register sched_clock callback
Date: Sat, 26 Apr 2014 01:22:17 +0200 [thread overview]
Message-ID: <535AEE29.5090108@gmail.com> (raw)
In-Reply-To: <1398331286-2020-1-git-send-email-vincent.guittot@linaro.org>
Hi Vincent,
On 24.04.2014 11:21, Vincent Guittot wrote:
> Use the clocksource mct-frc for sched_clock
>
> Signed-off-by: Vincent Guittot <vincent.guittot@linaro.org>
> ---
> drivers/clocksource/exynos_mct.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/drivers/clocksource/exynos_mct.c b/drivers/clocksource/exynos_mct.c
> index a6ee6d7..61b0577 100644
> --- a/drivers/clocksource/exynos_mct.c
> +++ b/drivers/clocksource/exynos_mct.c
> @@ -24,6 +24,7 @@
> #include <linux/of_irq.h>
> #include <linux/of_address.h>
> #include <linux/clocksource.h>
> +#include <linux/sched_clock.h>
>
> #define EXYNOS4_MCTREG(x) (x)
> #define EXYNOS4_MCT_G_CNT_L EXYNOS4_MCTREG(0x100)
> @@ -192,12 +193,19 @@ struct clocksource mct_frc = {
> .resume = exynos4_frc_resume,
> };
>
> +static u64 notrace exynos4_read_sched_clock(void)
> +{
> + return exynos4_frc_read(&mct_frc);
> +}
> +
> static void __init exynos4_clocksource_init(void)
> {
> exynos4_mct_frc_start(0, 0);
>
> if (clocksource_register_hz(&mct_frc, clk_rate))
> panic("%s: can't register clocksource\n", mct_frc.name);
> +
> + sched_clock_register(exynos4_read_sched_clock, 64, clk_rate);
> }
>
> static void exynos4_mct_comp0_stop(void)
>
Thanks for this patch.
Reviewed-by: Tomasz Figa <t.figa@samsung.com>
Best regards,
Tomasz
next prev parent reply other threads:[~2014-04-25 23:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 9:21 [PATCH] ARM: exynos: register sched_clock callback Vincent Guittot
2014-04-25 23:22 ` Tomasz Figa [this message]
2014-05-02 8:30 ` Daniel Lezcano
2014-05-02 13:24 ` Kukjin Kim
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=535AEE29.5090108@gmail.com \
--to=tomasz.figa@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).