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

2014-12-04 Thread Olof Johansson
On Wed, Oct 08, 2014 at 12:33:47AM -0700, Sonny Rao wrote: > From: 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

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

2014-12-04 Thread Olof Johansson
On Wed, Oct 08, 2014 at 12:33:47AM -0700, Sonny Rao wrote: From: Doug Anderson diand...@chromium.org 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. *

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

2014-11-28 Thread Catalin Marinas
On Wed, Nov 26, 2014 at 12:49:42PM +, Daniel Lezcano wrote: > On 10/08/2014 09:33 AM, Sonny Rao wrote: > > From: 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

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

2014-11-28 Thread Catalin Marinas
On Wed, Nov 26, 2014 at 12:49:42PM +, Daniel Lezcano wrote: On 10/08/2014 09:33 AM, Sonny Rao wrote: From: Doug Anderson diand...@chromium.org 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

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

2014-11-26 Thread Yingjoe Chen
Hi, On Wed, 2014-11-26 at 08:14 -0800, Doug Anderson wrote: > Yingjoe, > > On Wed, Nov 26, 2014 at 6:41 AM, Yingjoe Chen > wrote: > > Sorry for the (very) late reply. > > I just realize today MT8135 need this and the other patch [1] to boot > > SMP correctly. I've applied both patches and

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

2014-11-26 Thread Doug Anderson
Yingjoe, On Wed, Nov 26, 2014 at 6:41 AM, Yingjoe Chen wrote: > Sorry for the (very) late reply. > I just realize today MT8135 need this and the other patch [1] to boot > SMP correctly. I've applied both patches and they works fine. Thanks :) Excellent. It's helpful to include a Tested-by: tag

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

2014-11-26 Thread Yingjoe Chen
On Wed, 2014-10-08 at 15:33 +0800, Sonny Rao wrote: > From: 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

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

2014-11-26 Thread Daniel Lezcano
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,

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

2014-11-26 Thread Heiko Stübner
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,

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

2014-11-26 Thread 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

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

2014-11-26 Thread Daniel Lezcano
On 10/08/2014 09:33 AM, Sonny Rao wrote: From: 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

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

2014-11-26 Thread Heiko Stübner
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

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

2014-11-26 Thread 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

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

2014-11-26 Thread Heiko Stübner
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

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

2014-11-26 Thread 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 ? Thanks -- Daniel On 11/20/2014 12:01 AM, Doug Anderson

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

2014-11-26 Thread 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 ? Thanks -- Daniel On 11/20/2014 12:01 AM, Doug Anderson

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

2014-11-26 Thread Heiko Stübner
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

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

2014-11-26 Thread 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

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

2014-11-26 Thread Heiko Stübner
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.

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

2014-11-26 Thread Daniel Lezcano
On 10/08/2014 09:33 AM, Sonny Rao wrote: From: Doug Anderson diand...@chromium.org 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

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

2014-11-26 Thread 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

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

2014-11-26 Thread Heiko Stübner
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

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

2014-11-26 Thread Daniel Lezcano
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,

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

2014-11-26 Thread Yingjoe Chen
On Wed, 2014-10-08 at 15:33 +0800, Sonny Rao wrote: From: Doug Anderson diand...@chromium.org 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

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

2014-11-26 Thread Doug Anderson
Yingjoe, On Wed, Nov 26, 2014 at 6:41 AM, Yingjoe Chen yingjoe.c...@mediatek.com wrote: Sorry for the (very) late reply. I just realize today MT8135 need this and the other patch [1] to boot SMP correctly. I've applied both patches and they works fine. Thanks :) Excellent. It's helpful to

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

2014-11-26 Thread Yingjoe Chen
Hi, On Wed, 2014-11-26 at 08:14 -0800, Doug Anderson wrote: Yingjoe, On Wed, Nov 26, 2014 at 6:41 AM, Yingjoe Chen yingjoe.c...@mediatek.com wrote: Sorry for the (very) late reply. I just realize today MT8135 need this and the other patch [1] to boot SMP correctly. I've applied both

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

2014-11-23 Thread Daniel Lezcano
On 11/20/2014 12:01 AM, Doug Anderson wrote: Daniel, On Wed, Oct 8, 2014 at 12:33 AM, Sonny Rao wrote: From: 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

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

2014-11-23 Thread Daniel Lezcano
On 11/20/2014 12:01 AM, Doug Anderson wrote: Daniel, On Wed, Oct 8, 2014 at 12:33 AM, Sonny Rao sonny...@chromium.org wrote: From: Doug Anderson diand...@chromium.org Some 32-bit (ARMv7) systems are architected like this: * The firmware doesn't know and doesn't care about hypervisor mode and

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

2014-11-19 Thread Doug Anderson
Daniel, On Wed, Oct 8, 2014 at 12:33 AM, Sonny Rao wrote: > From: 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

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

2014-11-19 Thread Doug Anderson
Daniel, On Wed, Oct 8, 2014 at 12:33 AM, Sonny Rao sonny...@chromium.org wrote: From: Doug Anderson diand...@chromium.org 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

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

2014-10-08 Thread Sonny Rao
From: 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

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

2014-10-08 Thread Sonny Rao
From: Doug Anderson diand...@chromium.org 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