On 07.10.2013 11:34, Thierry Reding wrote: > The Tegra DRM driver currently uses some infrastructure to defer the DRM > core initialization until all required devices have registered. The same > infrastructure can potentially be used by any other driver that requires > more than a single sub-device of the host1x module. > > Make the infrastructure more generic and keep only the DRM specific code > in the DRM part of the driver. Eventually this will make it easy to move > the DRM driver part back to the DRM subsystem. Do we need the host1x_client/tegra_drm_client concept outside DRM? You separated the two in an earlier patch, but the whole structure is there because of limitation in DRM. Shouldn't we keep management of drm clients entirely inside drm? Second, do we need an own drm_bus for host1x clients? Does it bring something drm_platform doesn't? I couldn't see any immediate difference between the two. Terje -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
