Re: [PATCH] clocksource: arch_timer: Allow the device tree to specify the physical timer

2014-09-11 Thread Christopher Covington
On 09/11/2014 12:04 PM, Doug Anderson wrote: > Christopher, > > On Thu, Sep 11, 2014 at 8:58 AM, Christopher Covington > wrote: >> Hi Doug, >> >> On 09/11/2014 11:52 AM, Doug Anderson wrote: >>> Some 32-bit (ARMv7) systems are architected like this: >>> >>> * The firmware doesn't know and doesn't

Re: [PATCH] clocksource: arch_timer: Allow the device tree to specify the physical timer

2014-09-11 Thread Will Deacon
On Thu, Sep 11, 2014 at 05:04:11PM +0100, Doug Anderson wrote: > On Thu, Sep 11, 2014 at 8:58 AM, Christopher Covington > wrote: > > On 09/11/2014 11:52 AM, Doug Anderson wrote: > >> diff --git a/drivers/clocksource/arm_arch_timer.c > >> b/drivers/clocksource/arm_arch_timer.c > >> index 5163ec1..

Re: [PATCH] clocksource: arch_timer: Allow the device tree to specify the physical timer

2014-09-11 Thread Nathan Lynch
On 09/11/2014 10:58 AM, Christopher Covington wrote: > > On 09/11/2014 11:52 AM, Doug Anderson wrote: >> diff --git a/drivers/clocksource/arm_arch_timer.c >> b/drivers/clocksource/arm_arch_timer.c >> index 5163ec1..8ca07a9 100644 >> --- a/drivers/clocksource/arm_arch_timer.c >> +++ b/drivers/cloc

Re: [PATCH] clocksource: arch_timer: Allow the device tree to specify the physical timer

2014-09-11 Thread Doug Anderson
Christopher, On Thu, Sep 11, 2014 at 8:58 AM, Christopher Covington wrote: > Hi Doug, > > On 09/11/2014 11:52 AM, Doug Anderson wrote: >> Some 32-bit (ARMv7) systems are architected like this: >> >> * The firmware doesn't know and doesn't care about hypervisor mode and >> we don't want to add t

Re: [PATCH] clocksource: arch_timer: Allow the device tree to specify the physical timer

2014-09-11 Thread Christopher Covington
Hi Doug, On 09/11/2014 11:52 AM, Doug Anderson wrote: > Some 32-bit (ARMv7) systems are architected like this: > > * The firmware doesn't know and doesn't care about hypervisor mode and > we don't want to add the complexity of hypervisor there. > > * The firmware isn't involved in SMP bringup

[PATCH] clocksource: arch_timer: Allow the device tree to specify the physical timer

2014-09-11 Thread Doug Anderson
Some 32-bit (ARMv7) systems are architected like this: * The firmware doesn't know and doesn't care about hypervisor mode and we don't want to add the complexity of hypervisor there. * The firmware isn't involved in SMP bringup or resume. * The ARCH timer come up with an uninitialized offset b