Hi Daniel, On Wednesday 30 October 2013 16:53:22 Daniel Vetter wrote: > On Wed, Oct 30, 2013 at 4:32 PM, Sean Paul <seanpaul@xxxxxxxxxxxx> wrote: > > Once all required nodes have been "claimed", the main driver's probe > > would call drm_platform/pci_init to kick off load(). After load() has > > finished, the drm layer would then call the various standalone driver > > hooks that were previously registered when it claimed its node. These > > hooks would allow the driver to register its > > crtc/encoder/bridge/connector. > > Just a quick comment on calling the ->driver_load callback: I plan to > look again my "kill drm midlayer" series so that drivers are in full > control of the load sequence. Then they could do whatever delayed > loading the need to do by calling into optional helpers (hopefully > shared with asoc and v4l and other aggregate devices madness) and the > drm core simply does not need to care: The driver only > registers/allocates the drm_device once it's ready to do so. That would be great ! Please let me know if you would like me to test patches with the R-Car DU driver. -- Regards, Laurent Pinchart _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
