From: u.kleine-koenig@pengutronix.de (Uwe =?iso-8859-1?Q?Kleine-K=F6nig?=) Date: Tue, 5 Nov 2013 11:01:42 +0100 Subject: [PATCH v5 1/4] ARM: deprecate mach/timex.h for !ARCH_MULTIPLATFORM In-Reply-To: References: <20131105083336.GK14892@pengutronix.de> <1383642757-9762-1-git-send-email-u.kleine-koenig@pengutronix.de> Message-ID: <20131105100142.GM14892@pengutronix.de> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Tue, Nov 05, 2013 at 10:42:48AM +0100, Linus Walleij wrote: > On Tue, Nov 5, 2013 at 10:12 AM, Uwe Kleine-K?nig > wrote: > > > +config NEED_MACH_TIMEX_H > > + bool > > + help > > + Select this when mach/timex.h is required to provide special > > + definitions for this platform. This should be avoided when possible. > > OK this is no blocker, and do proceed with this as the kernel sure > looks better after this than before it. > > However as the next step I would prefer that we start to get rid of > all the NEED_MACH_FOO_H used for just refactoring out headers. > > Can we not completely do away with this header next, and provide > the services it supplied locally in the mach-foo folder for these machines > instead so we do not need to have all these Kconfig things and preserve > the namespace for them? > > The real trick is to make CLOCK_TICK_RATE and LATCH runtime > variables instead of a compile-time variables, right? Can't we do > this? Well, for LATCH there is no problem because it just uses CLOCK_TICK_RATE and if the latter is provided correctly there is no problem. However I don't see a way how to determine CLOCK_TICK_RATE at runtime. IMHO here you need to fix all users as I just did for the u300 timer code. Best regards Uwe -- Pengutronix e.K. | Uwe Kleine-K?nig | Industrial Linux Solutions | http://www.pengutronix.de/ |