Re: [PATCHv3 01/10] clocksource: add generic dummy timer driver

2013-04-04 Thread Stephen Boyd
On 03/26/13 04:28, Mark Rutland wrote: > On Tue, Mar 26, 2013 at 02:14:53AM +, Stephen Boyd wrote: >> Ok. Thanks for clearing up my confusion. >> >> Like you say, increasing the dummy timer rating seems like a hack. But >> it also sounds like you want to keep the dummy timer driver fully self >

Re: [PATCHv3 01/10] clocksource: add generic dummy timer driver

2013-03-26 Thread Mark Rutland
On Mon, Mar 25, 2013 at 08:47:42PM +, Thomas Gleixner wrote: > On Mon, 25 Mar 2013, Mark Rutland wrote: > > Thomas, do you have an idea of if/when tip/timers/urgent will hit mainline? > > Thanks for the reminder. I just sent a pull request Linuswards. Cheers! Mark. -- To unsubscribe from thi

Re: [PATCHv3 01/10] clocksource: add generic dummy timer driver

2013-03-26 Thread Mark Rutland
On Tue, Mar 26, 2013 at 02:14:53AM +, Stephen Boyd wrote: > On 03/25/13 11:00, Mark Rutland wrote: > > > >>> I've spent the last few hours trying to get the dummy_timer driver > >>> working on > >>> tc2 with the sp804 as the broadcast source (with architected timer support > >>> disabled). It

Re: [PATCHv3 01/10] clocksource: add generic dummy timer driver

2013-03-25 Thread Stephen Boyd
On 03/25/13 11:00, Mark Rutland wrote: > >>> I've spent the last few hours trying to get the dummy_timer driver working >>> on >>> tc2 with the sp804 as the broadcast source (with architected timer support >>> disabled). It turns out that having dummy timer's rating so low means that >>> it >>> w

Re: [PATCHv3 01/10] clocksource: add generic dummy timer driver

2013-03-25 Thread Thomas Gleixner
On Mon, 25 Mar 2013, Mark Rutland wrote: > Thomas, do you have an idea of if/when tip/timers/urgent will hit mainline? Thanks for the reminder. I just sent a pull request Linuswards. Thanks, tglx -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a

Re: [PATCHv3 01/10] clocksource: add generic dummy timer driver

2013-03-25 Thread Mark Rutland
On Mon, Mar 25, 2013 at 04:49:18PM +, Stephen Boyd wrote: > On 03/22/13 11:03, Mark Rutland wrote: > > On Thu, Mar 21, 2013 at 06:13:17PM +, Stephen Boyd wrote: > >> On 03/21/13 11:09, Mark Rutland wrote: > >>> Hi Stephen, > >>> > >>> I've just been trying to test the dummy timer, and reali

Re: [PATCHv3 01/10] clocksource: add generic dummy timer driver

2013-03-25 Thread Stephen Boyd
On 03/22/13 11:03, Mark Rutland wrote: > On Thu, Mar 21, 2013 at 06:13:17PM +, Stephen Boyd wrote: >> On 03/21/13 11:09, Mark Rutland wrote: >>> Hi Stephen, >>> >>> I've just been trying to test the dummy timer, and realised it's broken, as >>> it >>> registers a cpu notifier from a device_ini

Re: [PATCHv3 01/10] clocksource: add generic dummy timer driver

2013-03-22 Thread Mark Rutland
On Thu, Mar 21, 2013 at 06:13:17PM +, Stephen Boyd wrote: > On 03/21/13 11:09, Mark Rutland wrote: > > Hi Stephen, > > > > I've just been trying to test the dummy timer, and realised it's broken, as > > it > > registers a cpu notifier from a device_initcall (after SMP's been brought > > up),

Re: [PATCHv3 01/10] clocksource: add generic dummy timer driver

2013-03-21 Thread Stephen Boyd
On 03/21/13 11:09, Mark Rutland wrote: > Hi Stephen, > > I've just been trying to test the dummy timer, and realised it's broken, as it > registers a cpu notifier from a device_initcall (after SMP's been brought up), > and doesn't ensure all active CPUs have been set up. Evidently no-one else has >

Re: [PATCHv3 01/10] clocksource: add generic dummy timer driver

2013-03-21 Thread Mark Rutland
Hi Stephen, I've just been trying to test the dummy timer, and realised it's broken, as it registers a cpu notifier from a device_initcall (after SMP's been brought up), and doesn't ensure all active CPUs have been set up. Evidently no-one else has attempted to test it thus far, and I'm not able t