From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clocksource: sirf/marco+prima2: drop usage of CLOCK_TICK_RATE
Date: Thu, 14 Nov 2013 10:07:05 +0100 [thread overview]
Message-ID: <20131114090705.GX14892@pengutronix.de> (raw)
In-Reply-To: <5283DA74.9080402@linaro.org>
On Wed, Nov 13, 2013 at 09:00:52PM +0100, Daniel Lezcano wrote:
> On 11/11/2013 09:20 PM, Uwe Kleine-K?nig wrote:
> >As CSR SiRF is converted to multi platform CLOCK_TICK_RATE is a dummy
> >value that seems to match the right value is used.
> >(arch/arm/mach-prima2/include/mach/timex.h which defined CLOCK_TICK_RATE
> >to 1000000 was removed in commit cf82e0e (ARM: sirf: enable
> >multiplatform support); marco used the same file.)
> >
> >To not depend on that dummy value use a local #define instead.
>
> I don't get this patch. It is to fix a compilation error ?
No, the problem is that CLOCK_TICK_RATE used to be defined in a platform
specific header <mach/timex.h>. For the ARM multiplatform stuff, this
was dropped and now all multiplatform kernels use 1000000. For some
platform (like SiRF) this happens to be correct, but actually it's pure
luck. Further down the road I'd like to drop defining CLOCK_TICK_RATE
for all platforms, so this is a preparing patch. But even independant
from that it feels wrong to use a dummy value that was only introduced
to prevent compile breakage.
Would this change log be better:
Since CSR SiRF was converted to multi platform in cf82e0e (ARM:
sirf: enable multiplatform support) the symbol CLOCK_TICK_RATE
isn't the platform specific definition any more, but a global
dummy value. There was no harm introduced in cf82e0e because the
global value happens to match the old platform specific one,
still this dummy value isn't intended to be used and will
hopefully disappear soon, so introduce a local #define and use
that instead.
So it's not urgent, but would be a nice cleanup for 3.14-rc1.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2013-11-14 9:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 20:20 [PATCH] clocksource: sirf/marco+prima2: drop usage of CLOCK_TICK_RATE Uwe Kleine-König
2013-11-13 20:00 ` Daniel Lezcano
2013-11-14 9:07 ` Uwe Kleine-König [this message]
2013-11-26 13:55 ` Uwe Kleine-König
2013-11-28 7:34 ` Daniel Lezcano
2013-11-28 9:11 ` Uwe Kleine-König
2013-11-28 11:32 ` Daniel Lezcano
2013-11-28 13:21 ` [PATCH v2] " Uwe Kleine-König
2013-12-04 8:52 ` Uwe Kleine-König
2013-12-04 9:13 ` Daniel Lezcano
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=20131114090705.GX14892@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).