From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 1/2] AT91: Support SAM9260 and SAM9G20-based boards in the same kernel image
Date: Tue, 18 Jan 2011 15:32:41 +0000 [thread overview]
Message-ID: <20110118153241.GE9719@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20110118150030.GO14798@game.jcrosoft.org>
On Tue, Jan 18, 2011 at 04:00:30PM +0100, Jean-Christophe PLAGNIOL-VILLARD wrote:
> this idea is to do not have CONFIG_ARCH_AT91SAM9G20 anymore only 9260
>
> and detect it
>
> but the man issue is the CLOCK_TICK_RATE which is different between both of
> them except if we use a common one for those soc or the sam9/11 we could not
> put them in the same kernel
If you switch to clocksource/clockevents, then I think CLOCK_TICK_RATE
is irrelevant as time advances according to the interval measured by
the previous and current clocksource read, rather than 1/HZ intervals.
However, I'm never happy to say "just set CLOCK_TICK_RATE to some random
value that's a multiple of HZ" because I can't convince myself that these
don't have any effect when using clocksources. The list of symbols which
depend on CLOCK_TICK_RATE are:
ACTHZ
LATCH
TICK_NSEC
TICK_USEC_TO_NSEC
LOW_RES_NSEC
MONOTONIC_RES_NSEC
NSEC_PER_JIFFY
KTIME_LOW_RES
and if you grep for those outside of arch/, you find them being used in
a fair amount of code under kernel/, as well as the odd driver here and
there.
next prev parent reply other threads:[~2011-01-18 15:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-15 17:50 [RFC 1/2] AT91: Support SAM9260 and SAM9G20-based boards in the same kernel image Albin Tonnerre
2011-01-15 17:50 ` [RFC 2/2] AT91: Update board-cpu9krea to support the 9260/9G20 variants in a single image Albin Tonnerre
2011-01-17 7:50 ` Jean-Christophe PLAGNIOL-VILLARD
2011-01-17 9:02 ` Eric Bénard
2011-01-17 7:57 ` [RFC 1/2] AT91: Support SAM9260 and SAM9G20-based boards in the same kernel image Jean-Christophe PLAGNIOL-VILLARD
2011-01-18 7:00 ` Albin Tonnerre
2011-01-18 15:00 ` Jean-Christophe PLAGNIOL-VILLARD
2011-01-18 15:32 ` Russell King - ARM Linux [this message]
2011-01-18 17:18 ` Gilles Chanteperdrix
2011-01-18 17:43 ` Russell King - ARM Linux
2011-01-18 18:52 ` Jean-Christophe PLAGNIOL-VILLARD
2011-01-18 19:35 ` Russell King - ARM Linux
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=20110118153241.GE9719@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).