[PATCH v5 1/4] ARM: deprecate mach/timex.h for !ARCH_MULTIPLATFORM

[Uwe Kleine-König]

On Tue, Nov 05, 2013 at 01:26:31PM +0100, Arnd Bergmann wrote:
> On Tuesday 05 November 2013, Russell King - ARM Linux wrote:
> > On Tue, Nov 05, 2013 at 12:34:42PM +0100, Arnd Bergmann wrote:
> > > config CLOCK_TICK_RATE
> > >       int
> > >       depends on !ARCH_MULTIPLATFORM && ARCH_USES_GETTIMEOFFSET
> > >       depends on ARCH_GEMINI || ARCH_SA1100 || ARCH_EBSA110 || ARCH_EP93XX || ARCH_RPC || ARCH_AT91X40
> > >       default 40000000 if ARCH_AT91X40
> > >       default 38000000 if ARCH_GEMINI
> > >       default 3686400 if ARCH_SA1100
> > >       default 47894000 if ARCH_EBSA110
> > >       default 983040 if ARCH_EP93xx
> > >       default 2000000 if ARCH_RPC
> > >       # don't even think about adding more to this list, better get rid of the
> > >       # existing ones by converting them to proper clocksources
> > 
> > That's a pipedream.  It really is.  Some of those are impossible to
> > convert because you don't have enough timers/counters to provide the
> > clocksource and clockevents - as I've mentioned several times in the
> > past.
> 
> Do you mean removing all of the above is a pipedream, or using Kconfig like that?
> 
> I know we can't kill all of them, but there are still a few in the list above
> that can be made to use clocksource, and I'm fine with keeping the list
> around for the ones that really can't. The comment should probably be
> clearer, but it was more intended for people with random out-of-tree platform
> code that should be converted to use clocksource.
droping the CLOCK_TICK_RATE cpp symbol and converting to clocksource
doesn't necessarily need to go hand in hand, do they? If yes, can you
please point out the non-trivial use of CLOCK_TICK_RATE?

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |