[PATCHv2] omap3: beagle: Use GPTIMER1 for clockevents
Tony Lindgren
tony at atomide.com
Mon Jun 27 14:00:27 EDT 2011
* Premi, Sanjeev <premi at ti.com> [110627 06:24]:
>
> [sp] While I take my time understanding things on devel-timer;
> I had a quick question - at risk of being flamed.
>
> Adding a new machine ID would trickle to u-boot and same
> uImage (default) may not work across board revisions.
Yes that's a hassle :( Until we have device tree, maybe see if
u-boot passes ATAG_REVISION that's available as system_rev in
kernel?
> How does this scheme look like:
> - GPTIMER1 is used as default - as it works for most boards.
> - GPTIMER12 is used based on a static config option OR a
> board specific bootarg
>
> I know both these options aren't general practice. Still
> wanted to know your views in the current context.
Let's not do a Kconfig option, but a cmdline option should work
if done in a generic way. If you decide to go that way, then
please add that to timer.c against devel-timer branch.
Regards,
Tony
More information about the linux-arm-kernel
mailing list