On Fri, Dec 16, 2011 at 8:20 PM, Daniel Lezcano
wrote:
>> diff --git a/arch/arm/mach-ux500/clock.c b/arch/arm/mach-ux500/clock.c
>> index e832664..60378b3 100644
>> --- a/arch/arm/mach-ux500/clock.c
>> +++ b/arch/arm/mach-ux500/clock.c
>> @@ -743,7 +743,8 @@ err_out:
>> late_initcall(clk_debugfs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/16/2011 08:57 AM, Linus Walleij wrote:
> On Fri, Dec 16, 2011 at 6:56 AM, Daniel Lezcano
> wrote:
>> [Me]
>>> what happens if you just reactivate CPUfreq then use menuconfig
>>> to go into drivers/ directly you will see the
>>> "Clocksource PRCM
On Fri, Dec 16, 2011 at 6:56 AM, Daniel Lezcano
wrote:
> [Me]
>> what happens if you just reactivate CPUfreq then use menuconfig
>> to go into drivers/ directly you will see the
>> "Clocksource PRCMU Timer" (sorry the clksrc subsystem does not
>> have its own submenu...), deselect that so as to us
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/16/2011 12:23 AM, Linus Walleij wrote:
> On Thu, Dec 15, 2011 at 8:02 PM, john stultz wrote:
>> On Thu, 2011-12-15 at 14:06 +0100, Linus Walleij wrote:
>>> It means that the kernel idea of sleep(1) is, sleep atleast 1 second,
>>> possibly more.
On Thu, Dec 15, 2011 at 8:02 PM, john stultz wrote:
> On Thu, 2011-12-15 at 14:06 +0100, Linus Walleij wrote:
>> It means that the kernel idea of sleep(1) is, sleep atleast 1 second,
>> possibly more. When the system scales down frequency, say to half
>> the frequency, things start to take twice t
On Thu, 2011-12-15 at 14:06 +0100, Linus Walleij wrote:
> On Thu, Dec 15, 2011 at 1:16 PM, Daniel Lezcano
> wrote:
> > [Me]
> >>> It is easy to reproduce with 'time sleep 1' where the timer expires 1, 2
> >>> or 3 seconds later.
> >>>
> >>> It seems that does not happen with linux-linaro-3.1 but I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/15/2011 02:06 PM, Linus Walleij wrote:
> On Thu, Dec 15, 2011 at 1:16 PM, Daniel Lezcano
> wrote:
>> [Me]
It is easy to reproduce with 'time sleep 1' where the timer expires 1, 2
or 3 seconds later.
It seems that does not hap
On 15 December 2011 13:06, Linus Walleij wrote:
> On Thu, Dec 15, 2011 at 1:16 PM, Daniel Lezcano
> wrote:
>> [Me]
It is easy to reproduce with 'time sleep 1' where the timer expires 1, 2
or 3 seconds later.
It seems that does not happen with linux-linaro-3.1 but I was able to
On Thu, Dec 15, 2011 at 1:16 PM, Daniel Lezcano
wrote:
> [Me]
>>> It is easy to reproduce with 'time sleep 1' where the timer expires 1, 2
>>> or 3 seconds later.
>>>
>>> It seems that does not happen with linux-linaro-3.1 but I was able to
>>> reproduce the problem on a vanilla kernel 3.1.5.
>>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/14/2011 05:02 PM, Linus Walleij wrote:
> On Wed, Dec 14, 2011 at 4:27 PM, Daniel Lezcano
> wrote:
>
>> while trying the linux-next at the point it boots (commit
>> be9b7335e70696bee731c152429b1737e42fe163, after v3.2-rc4), I noticed the
>> time
On Wed, Dec 14, 2011 at 4:27 PM, Daniel Lezcano
wrote:
> while trying the linux-next at the point it boots (commit
> be9b7335e70696bee731c152429b1737e42fe163, after v3.2-rc4), I noticed the
> timers were not working properly with CONFIG_NO_HZ.
>
> It is easy to reproduce with 'time sleep 1' where
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
while trying the linux-next at the point it boots (commit
be9b7335e70696bee731c152429b1737e42fe163, after v3.2-rc4), I noticed the
timers were not working properly with CONFIG_NO_HZ.
It is easy to reproduce with 'time sleep 1' where the timer ex
12 matches
Mail list logo
