lkml.org 
[lkml]   [2013]   [Nov]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 5/7] clocksource/cadence_ttc: Overhaul clocksource frequency adjustment
On Tue, Nov 12, 2013 at 08:01:37PM +0100, Daniel Lezcano wrote:
> On 11/08/2013 10:21 PM, Soren Brinkmann wrote:
> >The currently used method adjusting the clocksource to a changing input
> >frequency does not work on kernels from 3.11 on.
> >The new approach is to keep the timer frequency as constant as possible.
> >I.e.
> > - due to the TTC's prescaler limitations, allow frequency changes
> > only if the frequency scales by a power of 2
> > - adjust the counter's divider on the fly when a frequency change
> > occurs
> >
> >When suspending though, the driver should not prevent rate changes in
> >order to allow the system to enter its low power state. For that
> >reason a PM notifier is added so rate changes can be ignored during
> >suspend/resume.
>
> It sounds very weird you have to add a PM notifier in this driver.
>
> Have you been facing an issue or do you assume it could happen ?
Yes, I have problems without it, which are probably Zynq specific
though.
When we suspend on Zynq, we bypass and power down PLLs, which is a
re-parent operation in the clock framework. This happens in early suspend
and triggers the clock notifiers. Due to the restrictions the TTC's
clock notifier applies to frequency changes, it would prevent the
re-parent operation even though we do not have to care about it in
suspend. The timer's own suspend/resume callbacks are called to
late/early and the PM notifier seemed to be the solution. But I'm open
to alternative approaches.

>
> >This limits cpufreq to scale by certain factors only.
> >But we may keep the time base somewhat constant, so that sleep() & co
> >keep working as expected, while supporting cpufreq and suspend.
> >
> >Signed-off-by: Soren Brinkmann <soren.brinkmann@xilinx.com>
> >---
> > drivers/clocksource/cadence_ttc_timer.c | 142 +++++++++++++++++++++++++++-----
> > 1 file changed, 122 insertions(+), 20 deletions(-)
> >
> >diff --git a/drivers/clocksource/cadence_ttc_timer.c b/drivers/clocksource/cadence_ttc_timer.c
> >index 68a336038d8f..421b942dd707 100644
> >--- a/drivers/clocksource/cadence_ttc_timer.c
> >+++ b/drivers/clocksource/cadence_ttc_timer.c
> >@@ -16,12 +16,14 @@
> > */
> >
> > #include <linux/clk.h>
> >+#include <linux/clk-provider.h>
> > #include <linux/interrupt.h>
> > #include <linux/clockchips.h>
> > #include <linux/of_address.h>
> > #include <linux/of_irq.h>
> > #include <linux/slab.h>
> > #include <linux/sched_clock.h>
> >+#include <linux/suspend.h>
> >
> > /*
> > * This driver configures the 2 16-bit count-up timers as follows:
> >@@ -52,6 +54,8 @@
> > #define TTC_CNT_CNTRL_DISABLE_MASK 0x1
> >
> > #define TTC_CLK_CNTRL_CSRC_MASK (1 << 5) /* clock source */
> >+#define TTC_CLK_CNTRL_PSV_MASK 0x1e
> >+#define TTC_CLK_CNTRL_PSV_SHIFT 1
> >
> > /*
> > * Setup the timers to use pre-scaling, using a fixed value for now that will
> >@@ -63,6 +67,8 @@
> > #define CLK_CNTRL_PRESCALE_EN 1
> > #define CNT_CNTRL_RESET (1 << 4)
> >
> >+#define MAX_F_ERR 50
> >+
> > /**
> > * struct ttc_timer - This definition defines local timer structure
> > *
> >@@ -82,8 +88,13 @@ struct ttc_timer {
> > container_of(x, struct ttc_timer, clk_rate_change_nb)
> >
> > struct ttc_timer_clocksource {
> >+ int scale_dir;
> >+ u32 scale_clk_ctrl_reg_old;
> >+ u32 scale_clk_ctrl_reg_new;
> >+ int suspending;
> > struct ttc_timer ttc;
> > struct clocksource cs;
> >+ struct notifier_block suspend_nb;
> > };
> >
> > #define to_ttc_timer_clksrc(x) \
> >@@ -228,33 +239,120 @@ static int ttc_rate_change_clocksource_cb(struct notifier_block *nb,
> > struct ttc_timer_clocksource *ttccs = container_of(ttc,
> > struct ttc_timer_clocksource, ttc);
> >
> >+ if (ttccs->suspending)
> >+ return NOTIFY_OK;
>
> I don't see how it couldn't be racy. What prevents suspend to occur
> right after this check ?
Well, in our case there are two situations which could trigger this
notifier.
1. cpufreq
2. suspend
As long as cpufreq is doing its stuff things should be okay and fine.
And suspend triggers the PM and clock notifier in the correct order,
which solves the issue I described above. So, it is not really pretty,
but works for me.

Sören


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2013-11-12 22:21    [W:0.084 / U:0.516 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site