public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vlad Zakharov <Vladislav.Zakharov@synopsys.com>
To: "tglx@linutronix.de" <tglx@linutronix.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "daniel.lezcano@linaro.org" <daniel.lezcano@linaro.org>,
	"john.stultz@linaro.org" <john.stultz@linaro.org>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	"linux-snps-arc@lists.infradead.org" 
	<linux-snps-arc@lists.infradead.org>
Subject: update timer frequencies
Date: Fri, 10 Mar 2017 09:17:21 +0000	[thread overview]
Message-ID: <1489137441.2333.46.camel@synopsys.com> (raw)

Hello,

I am trying to implement a cpufreq driver for ARC CPUs. 
The point is that ARC timers (including those are used for timekeeping) are driven by the same clock as ARC CPU core(s).

So if cpufreq driver changes CPU frequency timers frequency also updates. 
I added notification handler to ARC timer driver were I attempted to update clocksource frequency with
"__clocksource_update_freq_hz()" but I found that actually the frequency didn't update. 

During my further investigation I mentioned that timekeeping framework doesn't allow frequency changes for more than
11%. This is quiet frustratingly: ARC cores supports such adjustments themselves but current framework API doesn't give
us a chance to use this functionality and in fact it even forbids CPU frequency changes in runtime at all.

Maybe I am mistaken and there is some way to get this going? Or maybe we can add some minor changes to timekeeping
framework to resolve this issue (special flag that allows such changes or something like this?).

Thanks.

-- 
Best regards,
Vlad Zakharov <vzakhar@synopsys.com>

             reply	other threads:[~2017-03-10  9:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-10  9:17 Vlad Zakharov [this message]
2017-03-10 10:28 ` update timer frequencies Thomas Gleixner
2017-08-04  6:58   ` Vineet Gupta
2017-08-04  9:38     ` Peter Zijlstra

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=1489137441.2333.46.camel@synopsys.com \
    --to=vladislav.zakharov@synopsys.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-snps-arc@lists.infradead.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