From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/7] clocksource/cadence_ttc: Store timer frequency in driver data
Date: Tue, 12 Nov 2013 17:26:34 +0100 [thread overview]
Message-ID: <528256BA.7010801@linaro.org> (raw)
In-Reply-To: <1383945677-29674-4-git-send-email-soren.brinkmann@xilinx.com>
On 11/08/2013 10:21 PM, Soren Brinkmann wrote:
> It is not allowed to call clk_get_rate() from interrupt context. To
> avoid such calls the timer input frequency is stored in the driver's
> data struct which makes it accessible to the driver in any context.
>
> Signed-off-by: Soren Brinkmann <soren.brinkmann@xilinx.com>
> ---
Acked-by: Daniel Lezcano <daniel.lezcano@linaro.org>
> drivers/clocksource/cadence_ttc_timer.c | 21 +++++++++++++--------
> 1 file changed, 13 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/clocksource/cadence_ttc_timer.c b/drivers/clocksource/cadence_ttc_timer.c
> index b2bb3a4bc205..a92350b55d32 100644
> --- a/drivers/clocksource/cadence_ttc_timer.c
> +++ b/drivers/clocksource/cadence_ttc_timer.c
> @@ -67,11 +67,13 @@
> * struct ttc_timer - This definition defines local timer structure
> *
> * @base_addr: Base address of timer
> + * @freq: Timer input clock frequency
> * @clk: Associated clock source
> * @clk_rate_change_nb Notifier block for clock rate changes
> */
> struct ttc_timer {
> void __iomem *base_addr;
> + unsigned long freq;
> struct clk *clk;
> struct notifier_block clk_rate_change_nb;
> };
> @@ -196,9 +198,8 @@ static void ttc_set_mode(enum clock_event_mode mode,
>
> switch (mode) {
> case CLOCK_EVT_MODE_PERIODIC:
> - ttc_set_interval(timer,
> - DIV_ROUND_CLOSEST(clk_get_rate(ttce->ttc.clk),
> - PRESCALE * HZ));
> + ttc_set_interval(timer, DIV_ROUND_CLOSEST(ttce->ttc.freq,
> + PRESCALE * HZ));
> break;
> case CLOCK_EVT_MODE_ONESHOT:
> case CLOCK_EVT_MODE_UNUSED:
> @@ -273,6 +274,8 @@ static void __init ttc_setup_clocksource(struct clk *clk, void __iomem *base)
> return;
> }
>
> + ttccs->ttc.freq = clk_get_rate(ttccs->ttc.clk);
> +
> ttccs->ttc.clk_rate_change_nb.notifier_call =
> ttc_rate_change_clocksource_cb;
> ttccs->ttc.clk_rate_change_nb.next = NULL;
> @@ -298,16 +301,14 @@ static void __init ttc_setup_clocksource(struct clk *clk, void __iomem *base)
> __raw_writel(CNT_CNTRL_RESET,
> ttccs->ttc.base_addr + TTC_CNT_CNTRL_OFFSET);
>
> - err = clocksource_register_hz(&ttccs->cs,
> - clk_get_rate(ttccs->ttc.clk) / PRESCALE);
> + err = clocksource_register_hz(&ttccs->cs, ttccs->ttc.freq / PRESCALE);
> if (WARN_ON(err)) {
> kfree(ttccs);
> return;
> }
>
> ttc_sched_clock_val_reg = base + TTC_COUNT_VAL_OFFSET;
> - setup_sched_clock(ttc_sched_clock_read, 16,
> - clk_get_rate(ttccs->ttc.clk) / PRESCALE);
> + setup_sched_clock(ttc_sched_clock_read, 16, ttccs->ttc.freq / PRESCALE);
> }
>
> static int ttc_rate_change_clockevent_cb(struct notifier_block *nb,
> @@ -334,6 +335,9 @@ static int ttc_rate_change_clockevent_cb(struct notifier_block *nb,
> ndata->new_rate / PRESCALE);
> local_irq_restore(flags);
>
> + /* update cached frequency */
> + ttc->freq = ndata->new_rate;
> +
> /* fall through */
> }
> case PRE_RATE_CHANGE:
> @@ -367,6 +371,7 @@ static void __init ttc_setup_clockevent(struct clk *clk,
> if (clk_notifier_register(ttcce->ttc.clk,
> &ttcce->ttc.clk_rate_change_nb))
> pr_warn("Unable to register clock notifier.\n");
> + ttcce->ttc.freq = clk_get_rate(ttcce->ttc.clk);
>
> ttcce->ttc.base_addr = base;
> ttcce->ce.name = "ttc_clockevent";
> @@ -396,7 +401,7 @@ static void __init ttc_setup_clockevent(struct clk *clk,
> }
>
> clockevents_config_and_register(&ttcce->ce,
> - clk_get_rate(ttcce->ttc.clk) / PRESCALE, 1, 0xfffe);
> + ttcce->ttc.freq / PRESCALE, 1, 0xfffe);
> }
>
> /**
>
--
<http://www.linaro.org/> Linaro.org ? Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2013-11-12 16:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 21:21 [PATCH 0/7] arm: zynq: cpufreq support Soren Brinkmann
2013-11-08 21:21 ` [PATCH 1/7] arm: dt: zynq: Remove 'clock-ranges' from TTC nodes Soren Brinkmann
2013-11-12 15:29 ` Daniel Lezcano
2013-11-08 21:21 ` [PATCH 2/7] arm: dt: zynq: Add 'cpus' node Soren Brinkmann
2013-11-11 18:57 ` Sudeep KarkadaNagesha
2013-11-12 18:06 ` Sören Brinkmann
2013-11-12 21:58 ` Sören Brinkmann
2013-11-13 9:54 ` Sudeep KarkadaNagesha
2013-11-08 21:21 ` [PATCH 3/7] clocksource/cadence_ttc: Store timer frequency in driver data Soren Brinkmann
2013-11-12 16:26 ` Daniel Lezcano [this message]
2013-11-08 21:21 ` [PATCH 4/7] clocksource/cadence_ttc: Adjust interval in clock notifier Soren Brinkmann
2013-11-12 16:29 ` Daniel Lezcano
2013-11-22 18:06 ` Sören Brinkmann
2013-11-08 21:21 ` [PATCH 5/7] clocksource/cadence_ttc: Overhaul clocksource frequency adjustment Soren Brinkmann
2013-11-12 19:01 ` Daniel Lezcano
2013-11-12 21:13 ` Sören Brinkmann
2013-11-13 8:03 ` Viresh Kumar
2013-11-13 10:29 ` Daniel Lezcano
2013-11-13 17:14 ` Sören Brinkmann
2013-11-23 1:30 ` Sören Brinkmann
2013-11-08 21:21 ` [PATCH 6/7] clocksource/cadence_ttc: Use only one counter Soren Brinkmann
2013-11-08 21:21 ` [PATCH 7/7] arm: zynq: Add support for cpufreq Soren Brinkmann
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=528256BA.7010801@linaro.org \
--to=daniel.lezcano@linaro.org \
--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).