linux-kernel - clocksource with changing frequency?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <f5e5d3d7-699d-4f89-80c8-849e432e8b26@VA3EHSMHS017.ehs.local>
Date:	Thu, 20 Jun 2013 17:01:22 -0700
From:	Sören Brinkmann <soren.brinkmann@...inx.com>
To:	John Stultz <john.stultz@...aro.org>,
	Thomas Gleixner <tglx@...utronix.de>
CC:	Sören Brinkmann <soren.brinkmann@...inx.com>,
	<linux-kernel@...r.kernel.org>,
	<linux-arm-kernel@...ts.infradead.org>,
	Michal Simek <michal.simek@...inx.com>
Subject: clocksource with changing frequency?

Hi all,

I have a question/problem with a clocksource whose input frequency can
change.
On Zynq we use the cadece_ttc timer as clocksource. Its input clock is
tightly coupled to the CPU clock. I.e. it changes when cpufreq scales
the CPU clocks.
To compensate this, I added a clock notifier doing this on a frequency
change:
	clocksource_unregister(&ttccs->cs);                              
	clocksource_register_hz(&ttccs->cs, ndata->new_rate / PRESCALE);

This just seems not to be the most elegant way, a heavy weight operation
and results in a couple of locking errors in combination with
suspend/hotplug.

Is there a sane solution for such a case? E.g. for clockevent devices
there is a 'clockevents_update_freq()' to adjust to changing
frequencies.

I assume the sanest solution is an external oscillator as clock input,
but I think our platforms don't provide that :(

	Thanks,
	Sören


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