On Mon, Feb 24, 2014 at 05:56:38PM +0100, Philipp Zabel wrote: > Am Montag, den 24.02.2014, 15:49 +0000 schrieb Russell King - ARM Linux: > One issue was that the DT parsing code would try to add the imx-ldb > component right after the first crtc, and then its bind would fail > in imx_drm_encoder_parse_of because the three remaining crtcs were > not yet registered. This is already fixed by adding the crtc > components first. That's what happens anyway - we add /all/ the CRTCs first before we start adding the connectors. That means the CRTCs will be bound before the connectors (ldb). What you're probably missing is that with what's in my branch, if you want both CRTCs or the second CRTC in the IPU pair, you must specify both in the "crtcs" property - iow "crtcs = <&ipuX 0>, <&ipuX 1>". The reason is there's no way to differentiate the individual platform devices there without delving into the platform data. -- FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly improving, and getting towards what was expected from it. _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
