Sebastian Hesselbarth писал 03.05.2015 13:58:
On 03.05.2015 12:18, Andrew wrote:
[...]
Sorry for the long delay with testing, but here come the results.
I've rebased everything to 4.1-rc1
1. WFI + DeepIdle => freeze after approx:
* 1 hours and 30 minutes, first test
* 3 hours and 40 minut
On 20/04/2015 17:15, Andrew wrote:
> Gregory CLEMENT писал 20.04.2015 18:04:
>> Hi Andrew,
>>
>> On 13/04/2015 16:32, Andrew wrote:
>>> Gregory CLEMENT писал 13.04.2015 17:16:
Hi Andrew(s),
On 12/04/2015 21:47, Andrew Lunn wrote:
> On Sun, Apr 12, 2015 at 06:41:31PM +0300, Andrew
Gregory CLEMENT писал 20.04.2015 18:04:
Hi Andrew,
On 13/04/2015 16:32, Andrew wrote:
Gregory CLEMENT писал 13.04.2015 17:16:
Hi Andrew(s),
On 12/04/2015 21:47, Andrew Lunn wrote:
On Sun, Apr 12, 2015 at 06:41:31PM +0300, Andrew wrote:
Andrew Lunn ?? 12.04.2015 17:58:
Okay, got it.
Hi Andrew,
On 13/04/2015 16:32, Andrew wrote:
> Gregory CLEMENT писал 13.04.2015 17:16:
>> Hi Andrew(s),
>>
>> On 12/04/2015 21:47, Andrew Lunn wrote:
>>> On Sun, Apr 12, 2015 at 06:41:31PM +0300, Andrew wrote:
Andrew Lunn ?? 12.04.2015 17:58:
>> Okay, got it.
>> I'll file a b
Gregory CLEMENT писал 13.04.2015 17:16:
Hi Andrew(s),
On 12/04/2015 21:47, Andrew Lunn wrote:
On Sun, Apr 12, 2015 at 06:41:31PM +0300, Andrew wrote:
Andrew Lunn ?? 12.04.2015 17:58:
Okay, got it.
I'll file a bug about this issue to the the bugzilla. However
something
tells me it migh
Hi Andrew(s),
On 12/04/2015 21:47, Andrew Lunn wrote:
> On Sun, Apr 12, 2015 at 06:41:31PM +0300, Andrew wrote:
>> Andrew Lunn ?? 12.04.2015 17:58:
Okay, got it.
I'll file a bug about this issue to the the bugzilla. However
something
tells me it might not be cpuidle, bu
On Sun, Apr 12, 2015 at 06:41:31PM +0300, Andrew wrote:
> Andrew Lunn ?? 12.04.2015 17:58:
> >>Okay, got it.
> >>I'll file a bug about this issue to the the bugzilla. However
> >>something
> >>tells me it might not be cpuidle, but D-link. This one's sounds nasty
> >>and it has been around s
Andrew Lunn писал 12.04.2015 17:58:
Okay, got it.
I'll file a bug about this issue to the the bugzilla. However
something
tells me it might not be cpuidle, but D-link. This one's sounds nasty
and it has been around since 3.16.x. How could it go unnoticed?
Unfortunately I have no other armada-37
> Okay, got it.
> I'll file a bug about this issue to the the bugzilla. However something
> tells me it might not be cpuidle, but D-link. This one's sounds nasty
> and it has been around since 3.16.x. How could it go unnoticed?
> Unfortunately I have no other armada-370 hardware to test it.
Hi And
Sebastian Hesselbarth писал 12.04.2015 15:16:
On 12.04.2015 13:43, Andrew wrote:
Sebastian Hesselbarth писал 12.04.2015 14:20:
On 11.04.2015 22:29, Andrew Andrianov wrote:
Signed-off-by: Andrew Andrianov
[...]
+ * CONFIG_ARM_MVEBU_V7_CPUIDLE=y causes hard freezes every 1-8
hours
I don't t
On 12.04.2015 13:43, Andrew wrote:
Sebastian Hesselbarth писал 12.04.2015 14:20:
On 11.04.2015 22:29, Andrew Andrianov wrote:
Signed-off-by: Andrew Andrianov
[...]
+ * CONFIG_ARM_MVEBU_V7_CPUIDLE=y causes hard freezes every 1-8 hours
I don't think the dts is the right place for Linux issue
Sebastian Hesselbarth писал 12.04.2015 14:20:
On 11.04.2015 22:29, Andrew Andrianov wrote:
Signed-off-by: Andrew Andrianov
Andrew,
thanks for providing this dts, please _always_ add a commit log
describing what the patch is about. The introduction in the cover
letter is nice, but it will be
12 matches
Mail list logo
