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. 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? 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 > -- Gregory Clement, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
