Re: [PATCH v4] clocksource: arch_timer: Allow the device tree to specify uninitialized timer registers

From: Daniel Lezcano
Date: Wed Nov 26 2014 - 07:53:32 EST


On 11/26/2014 01:55 PM, Heiko StÃbner wrote:
Am Mittwoch, 26. November 2014, 13:49:57 schrieb Daniel Lezcano:
On 11/26/2014 01:48 PM, Heiko StÃbner wrote:
Am Mittwoch, 26. November 2014, 13:30:58 schrieb Daniel Lezcano:
On 11/26/2014 01:06 PM, Heiko StÃbner wrote:
Hi Daniel,

Am Mittwoch, 26. November 2014, 12:51:08 schrieb Daniel Lezcano:
Hi Doug, Olof,

IIUC, it sounds like this patch is needed from some other patches in
arm-soc. Olof was proposing to take this patch through its tree to
facilitate the integration.

Olof, is it this patch you were worried about ?

I think this is one of two patches in question.

"clocksource: arch_timer: Fix code to use physical timers when
requested"
[0] would be the second one.

And the patch for arm-soc that Olof means would be "ARM: dts: rk3288:
add
arm,cpu-registers-not-fw-configured" [1].

Ok, so IIUC, "clocksource: arch_timer: Fix code to use physical timers
when requested" should go via arm's tree, right ?

If I'm reading Olof's irc-comments from yesterday correctly, that is right
and the 3 patches should go in together:

- "clocksource: arch_timer: Fix code to use physical timers

when requested" fixes the use of physical timers in general

- "clocksource: arch_timer: Allow the device tree to specify uninitialized

timer registers" allows this to be set from dt

- "ARM: dts: rk3288: add arm,cpu-registers-not-fw-configured" enables this
on>
rk3288

Ok, then I drop them from my tree and will let Olof to handle them.

But maybe you could give them an Ack :-)

Already done :)

-- Daniel

--
<http://www.linaro.org/> Linaro.org â Open source software for ARM SoCs

Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/