On Fri, Jan 10, 2014 at 11:23:37PM +0000, Russell King - ARM Linux wrote:
> We do this in DT by providing a "superdevice" node which specifies
> the components, eg:
>
> imx-drm {
> compatible = "fsl,drm";
> crtcs = <&ipu1>;
> connectors = <&hdmi>;
> };
Saschas comment from 20140109074030.GN6750@xxxxxxxxxxxxxx isn't
addressed yet:
Sascha Hauer wrote:
> Can we have an example with a different number of
> encoders/connectors/crtcs, like:
>
> exynos-drm {
> compatible = "exynos,drm";
> crtcs = <&fimd1>;
> encoders = <&dp1>, <&hdmi1>, <&lvds1>;
> connectors = <&ptn3460>, <&hdmi1>;
> };
>
> Otherwise I get the impression that there is some topology of the
> components or at least relationship between the components encoded
> into the binding.
If I remember correctly, Sascha+Philipp+Lucas still had issues with the
bindings, but I'm not sure if they have been already addressed.
It's no good timing to finalize this during the weekend, where most
people are not in the office :)
rsc
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxx
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
