Hi,
在 2014年08月29日 19:22, Mark Rutland 写道:
>> 在 2014年08月28日 23:11, Mark Rutland 写道:
>>> To clarify: if there are low power states that the CPU can enter where
>>> we lose state, then this patch isn't correct.
>> Right now, the software of RK3288 SoC only support CPU hotplug
>> (cpu_on/off) and
On Fri, Aug 29, 2014 at 04:06:40AM +0100, Huang Tao wrote:
> Hi, Mark:
Hi,
> 在 2014年08月28日 23:11, Mark Rutland 写道:
> > To clarify: if there are low power states that the CPU can enter where
> > we lose state, then this patch isn't correct.
> Right now, the software of RK3288 SoC only support CPU
On Fri, Aug 29, 2014 at 04:06:40AM +0100, Huang Tao wrote:
Hi, Mark:
Hi,
在 2014年08月28日 23:11, Mark Rutland 写道:
To clarify: if there are low power states that the CPU can enter where
we lose state, then this patch isn't correct.
Right now, the software of RK3288 SoC only support CPU
Hi,
在 2014年08月29日 19:22, Mark Rutland 写道:
在 2014年08月28日 23:11, Mark Rutland 写道:
To clarify: if there are low power states that the CPU can enter where
we lose state, then this patch isn't correct.
Right now, the software of RK3288 SoC only support CPU hotplug
(cpu_on/off) and power off all
Hi, Mark:
在 2014年08月28日 23:11, Mark Rutland 写道:
> To clarify: if there are low power states that the CPU can enter where
> we lose state, then this patch isn't correct.
Right now, the software of RK3288 SoC only support CPU hotplug
(cpu_on/off) and power off all CPUs on suspend.
We do not
Mark,
Thanks for your reply and advice.
On 08/28/2014 11:11 PM, Mark Rutland wrote:
On Thu, Aug 28, 2014 at 10:17:58AM +0100, Mark Rutland wrote:
Hi Kever,
On Thu, Aug 28, 2014 at 02:40:17AM +0100, Kever Yang wrote:
We need use the hrtimer, which need the arch-timer to be 'always-on'
I
On Thu, Aug 28, 2014 at 10:17:58AM +0100, Mark Rutland wrote:
> Hi Kever,
>
> On Thu, Aug 28, 2014 at 02:40:17AM +0100, Kever Yang wrote:
> > We need use the hrtimer, which need the arch-timer to be 'always-on'
>
> I asked a question on the last posting [1]. Can you please confirm
> either way?
Hi Kever,
On Thu, Aug 28, 2014 at 02:40:17AM +0100, Kever Yang wrote:
> We need use the hrtimer, which need the arch-timer to be 'always-on'
I asked a question on the last posting [1]. Can you please confirm
either way?
Thanks,
Mark.
[1]
Hi Kever,
On Thu, Aug 28, 2014 at 02:40:17AM +0100, Kever Yang wrote:
We need use the hrtimer, which need the arch-timer to be 'always-on'
I asked a question on the last posting [1]. Can you please confirm
either way?
Thanks,
Mark.
[1]
On Thu, Aug 28, 2014 at 10:17:58AM +0100, Mark Rutland wrote:
Hi Kever,
On Thu, Aug 28, 2014 at 02:40:17AM +0100, Kever Yang wrote:
We need use the hrtimer, which need the arch-timer to be 'always-on'
I asked a question on the last posting [1]. Can you please confirm
either way?
Mark,
Thanks for your reply and advice.
On 08/28/2014 11:11 PM, Mark Rutland wrote:
On Thu, Aug 28, 2014 at 10:17:58AM +0100, Mark Rutland wrote:
Hi Kever,
On Thu, Aug 28, 2014 at 02:40:17AM +0100, Kever Yang wrote:
We need use the hrtimer, which need the arch-timer to be 'always-on'
I
Hi, Mark:
在 2014年08月28日 23:11, Mark Rutland 写道:
To clarify: if there are low power states that the CPU can enter where
we lose state, then this patch isn't correct.
Right now, the software of RK3288 SoC only support CPU hotplug
(cpu_on/off) and power off all CPUs on suspend.
We do not implement
We need use the hrtimer, which need the arch-timer to be 'always-on'
Signed-off-by: Kever Yang
---
arch/arm/boot/dts/rk3288.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/boot/dts/rk3288.dtsi b/arch/arm/boot/dts/rk3288.dtsi
index 5950b0a..698e6ea 100644
---
Hi,
On Wed, Aug 27, 2014 at 02:47:40AM +0100, Kever Yang wrote:
> We need use the hrtimer, which need the arch-timer to be 'always-on'
Just to check: it isn't possible to place CPUs in the rk3288 SoC into
low power states where their timers lose state and/or might not fire?
Mark.
>
Hi,
On Wed, Aug 27, 2014 at 02:47:40AM +0100, Kever Yang wrote:
We need use the hrtimer, which need the arch-timer to be 'always-on'
Just to check: it isn't possible to place CPUs in the rk3288 SoC into
low power states where their timers lose state and/or might not fire?
Mark.
We need use the hrtimer, which need the arch-timer to be 'always-on'
Signed-off-by: Kever Yang kever.y...@rock-chips.com
---
arch/arm/boot/dts/rk3288.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/boot/dts/rk3288.dtsi b/arch/arm/boot/dts/rk3288.dtsi
index 5950b0a..698e6ea
We need use the hrtimer, which need the arch-timer to be 'always-on'
Signed-off-by: Kever Yang
---
arch/arm/boot/dts/rk3288.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/boot/dts/rk3288.dtsi b/arch/arm/boot/dts/rk3288.dtsi
index 5950b0a..698e6ea 100644
---
We need use the hrtimer, which need the arch-timer to be 'always-on'
Signed-off-by: Kever Yang kever.y...@rock-chips.com
---
arch/arm/boot/dts/rk3288.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/boot/dts/rk3288.dtsi b/arch/arm/boot/dts/rk3288.dtsi
index 5950b0a..698e6ea
18 matches
Mail list logo
