Re: N950 boot/DRM issues with v4.16

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On Wed, Apr 18, 2018 at 12:20:43AM +0300, Aaro Koskinen wrote:
> When moving from 4.15 -> 4.16, I see long delays and spam from DRM in dmesg.
> 
> Is this some known issue, or should I try to e.g. bisect it? FWIW, the same
> kernel binary works on N900.

Apparently N950 display support got enabled in the DTS before it was actually
working. I did the following and the boot is as before:

diff --git a/arch/arm/boot/dts/omap3-n950.dts b/arch/arm/boot/dts/omap3-n950.dts
index 2354e09343f3..aa757482d572 100644
--- a/arch/arm/boot/dts/omap3-n950.dts
+++ b/arch/arm/boot/dts/omap3-n950.dts
@@ -231,6 +231,7 @@
 	lcd0: display {
 		compatible = "nokia,himalaya", "panel-dsi-cm";
 		label = "lcd0";
+		status = "disabled";
 
 		pinctrl-names = "default";
 		pinctrl-0 = <&display_pins>;

(Having in enabled in DTS will break my testing, as I want to use the
same kernel binary/configuration also for N900/N950/N9).

A.
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux