On Wed, Oct 30, 2013 at 4:32 PM, Sean Paul seanpaul@chromium.org 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. -Daniel