Re: Fwd: Re: [PATCH 2/2] ARM: mvebu: dts: Add dts file for DLink DNS-327L

From: Andrew
Date: Wed May 06 2015 - 09:40:34 EST


Gregory CLEMENT ÐÐÑÐÐ 06.05.2015 15:13:
Hi Andrew,



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 minutes, second test
2. WFI only (DeepIdle disabled via sysfs) => Still alive after 13 hours
and counting

Thanks for testing it. So, to sum-up, WFI+DeepIdle makes the board freeze
after a few hours in 4.1-rc1 and 4.0 for sure. Are you aware of any version
that did not freeze? It would help to know if it was a regression or not.

I've been observing it since 3.16 or so, when I first got mainline running on
the box. So my guess would be that it is NOT a regression.

Andrew Lunn did not report any issue on his 370RD however I will test
it also on an other Armada 370 base board (a Mirabox) using the .config
you already sent.

But what I expect is either a hardware issue, or a hardware configuration
issue in U-Boot. We still rely a lot on the bootloader and I fear that
we have some implicit assumptions.

By the way do you have access on the bootloader sources or at least could
you give us the U-boot version used?

AFAIK there's no GPL source drop for DNS-327L just yet. I'm using stock uboot:

U-Boot 2009.08-00043-gcfe3b76-dirty (Dec 03 2012 - 15:27:58)
Marvell version: 1.1.2 NQ.DNS-327.01

Didn't risk to burn upstream u-boot, just in case the hardware required any
special hacks to work.

Thanks,

Gregory




The proper patchset will follow as soon as I figure out what change
broke
dns320l-daemon (The utility that speaks to weltrend mcu on ttyS1)
It was working on 3.18.6, on 3.19 and up - it writes data to the port
(and mcu acks it),
but can't read any responses.

Same thing happens to the python (pyserial inside) implementation of the
fan-daemon:
https://github.com/martignlo/DNS-320L


--
Regards,
Andrew
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/