2013/4/1 Ning Jiang :
> 2013/4/1 Daniel Lezcano :
>> On 03/29/2013 10:24 AM, ning.n.ji...@gmail.com wrote:
>>> From: Ning Jiang
>>>
>>> Currently there are two problems when we try to stop local timer.
>>> First, it calls set_mode function directly so mode state is not
>>> updated for the clock ev
2013/4/1 Daniel Lezcano :
> On 03/29/2013 10:24 AM, ning.n.ji...@gmail.com wrote:
>> From: Ning Jiang
>>
>> Currently there are two problems when we try to stop local timer.
>> First, it calls set_mode function directly so mode state is not
>> updated for the clock event device. Second, it makes t
2013/4/1 Daniel Lezcano :
> On 03/29/2013 10:24 AM, ning.n.ji...@gmail.com wrote:
>> From: Ning Jiang
>>
>> Currently there are two problems when we try to stop local timer.
>> First, it calls set_mode function directly so mode state is not
>> updated for the clock event device. Second, it makes t
On 03/29/2013 10:24 AM, ning.n.ji...@gmail.com wrote:
> From: Ning Jiang
>
> Currently there are two problems when we try to stop local timer.
> First, it calls set_mode function directly so mode state is not
> updated for the clock event device. Second, it makes the device
> unused instead of sh
On 03/29/2013 10:24 AM, ning.n.ji...@gmail.com wrote:
> From: Ning Jiang
>
> Currently there are two problems when we try to stop local timer.
> First, it calls set_mode function directly so mode state is not
> updated for the clock event device. Second, it makes the device
> unused instead of sh
2013/3/30 Ning Jiang :
> 2013/3/30 Russell King - ARM Linux :
>> On Sat, Mar 30, 2013 at 05:57:38PM +0800, Ning Jiang wrote:
>>> 2013/3/30 Stephen Boyd :
>>> > On 03/29/13 02:24, ning.n.ji...@gmail.com wrote:
>>> >> From: Ning Jiang
>>> >>
>>> >> Currently there are two problems when we try to sto
2013/3/30 Russell King - ARM Linux :
> On Sat, Mar 30, 2013 at 05:57:38PM +0800, Ning Jiang wrote:
>> 2013/3/30 Stephen Boyd :
>> > On 03/29/13 02:24, ning.n.ji...@gmail.com wrote:
>> >> From: Ning Jiang
>> >>
>> >> Currently there are two problems when we try to stop local timer.
>> >> First, it
On Sat, Mar 30, 2013 at 05:57:38PM +0800, Ning Jiang wrote:
> 2013/3/30 Stephen Boyd :
> > On 03/29/13 02:24, ning.n.ji...@gmail.com wrote:
> >> From: Ning Jiang
> >>
> >> Currently there are two problems when we try to stop local timer.
> >> First, it calls set_mode function directly so mode stat
2013/3/30 Stephen Boyd :
> On 03/29/13 02:24, ning.n.ji...@gmail.com wrote:
>> From: Ning Jiang
>>
>> Currently there are two problems when we try to stop local timer.
>> First, it calls set_mode function directly so mode state is not
>> updated for the clock event device. Second, it makes the dev
On 03/29/13 02:24, ning.n.ji...@gmail.com wrote:
> From: Ning Jiang
>
> Currently there are two problems when we try to stop local timer.
> First, it calls set_mode function directly so mode state is not
> updated for the clock event device. Second, it makes the device
> unused instead of shutdown
From: Ning Jiang
Currently there are two problems when we try to stop local timer.
First, it calls set_mode function directly so mode state is not
updated for the clock event device. Second, it makes the device
unused instead of shutdown.
A subtle error will happen because of it. When a cpu is p
11 matches
Mail list logo