On 06/29/2014 11:35 PM, Russell King - ARM Linux wrote:
On Sun, Jun 29, 2014 at 10:59:47PM +0200, Andrew Lunn wrote:
This patchset removes arch/arm/mach-kirkwood and arch/arm/mach-dove. These SoCs are now supported in arch/arm/mach-mvebu using device tree.
Change the dependencies for a number of drivers, either to use ARCH_MVEBU where the drivers are generic, or MACH_KIRKWOOD and MACH_DOVE where the drivers are specific to a SoC.
Andrew Lunn (13): ARM: Kirkwood: Remove mach-kirkwood ARM: Dove: Remove mach-dove
There is actually a cubox regression which has yet to be tracked down. Running with my kernel (which is not-DT based) runs perfectly. With DT, HDMI output can be unstable.
One of the problems is that it's /very/ difficult to reproduce, but it is reproducable. I've seen it on two days over many reboots, and I've proved it by switching back and forth. DT sometimes suffers from the problem, whereas non-DT /never/ does.
Sebastian is aware of this, and as yet we haven't found a solution, nor have we found a way to reliably reproduce it.
I am aware of the issue but have not been able to reproduce it. Also, we have no /official/ non-DT CuBox support in mainline Linux at all. I understand that removing non-DT mach-dove currently is not your most preferred patch but from a mainline POV, mach-dove isn't actively used. The three officially supported boards have been converted to DT months ago and haven't received any TLC since then, so I doubt they are used by anyone.
My current impression of the issue is that it is more related with driver load order/missing delays for clocks/ignoring IP behavior on clock rate change or something like it.
Can you give a /rough/ schedule for your plans to sort out your private branches? If we can all investigate the issue with the same code basis, I am sure we can make DT dove behave the same way non-DT dove seems to be.
Sebastian