outcome of DRM/KMS DT bindings session

[Mark Brown]

On Fri, Nov 01, 2013 at 10:10:41AM +1000, Dave Airlie wrote:

> > Still the different components can be multiple devices, just initialize
> > the drm device once all components are probed. Remove it again once a

> But why? why should we have separate drivers for each component of a
> tightly coupled SoC?

> it makes no sense, having a driver node per every block in the chip
> isn't an advantage, it complicates
> things for no advantage at all. If we don't have hotplug hw removing
> one device shouldn't be possible
> this idea that removing a sub-driver should teardown the drm is crazy as well.

One case where this may be required is for integration with SoC power
domains where the DRM components are split between multiple domains (and
it may be more idiomatic even if they aren't).  If the SoC is using
power domains then it will expect to see at least one device within each
domain that gets used to reference count the activity for the domain.

This could just be a composite device per domain though.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20131031/b6967167/attachment.pgp>