i915_driver_load registers a component master and i915 driver registration is moved into the bind call of that component master. If any component of the particular features are registered with this I915 component master's match, then I915 registration will wait until all registered components are added to the framework. In third patch component from mei_hdcp module is registered to component_match of I915 master component. Hence I915 registration will wait until mei device is binded with mei_hdcp driver and adds the component to the component framework. Ramalingam C (3): component: alloc component_match without any comp to match drm/i915: component master at i915 driver load drm/i915: Initialize HDCP2.2 and its MEI interface drivers/base/component.c | 30 ++++++++++++++ drivers/gpu/drm/i915/i915_drv.c | 87 +++++++++++++++++++++++++++++++++------ drivers/gpu/drm/i915/i915_drv.h | 3 ++ drivers/gpu/drm/i915/intel_dp.c | 3 +- drivers/gpu/drm/i915/intel_drv.h | 5 ++- drivers/gpu/drm/i915/intel_hdcp.c | 78 ++++++++++++++++++++++++++++++++++- drivers/gpu/drm/i915/intel_hdmi.c | 2 +- include/drm/i915_component.h | 76 ++++++++++++++++++++++++++++++++++ include/linux/component.h | 2 + 9 files changed, 270 insertions(+), 16 deletions(-) -- 2.7.4 _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
