[PATCH 5/7] clocksource/cadence_ttc: Overhaul clocksource frequency adjustment
soren.brinkmann at xilinx.com
Fri Nov 22 20:30:59 EST 2013
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.
> > - 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
> 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 ?
As I said in my other email, we do have some issues related with
suspend. The construct with the PM notifier seemed to work but since we
upgraded our vendor tree to 3.12 I see issues with this code.
So, for now, I'll remove the PM notifier and associated code from this
I have to revisit the suspend case later.
More information about the linux-arm-kernel