From: Ramalingam C <ramalingam.c@intel.com>
To: intel-gfx@lists.freedesktop.org, daniel@ffwll.ch,
tomas.winkler@intel.com, alexander.usyskin@intel.com
Subject: [RFC 0/3] I915 component master
Date: Wed, 11 Jul 2018 19:41:25 +0530 [thread overview]
Message-ID: <1531318288-23380-1-git-send-email-ramalingam.c@intel.com> (raw)
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@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2018-07-11 14:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-11 14:11 Ramalingam C [this message]
2018-07-11 14:11 ` [RFC 1/3] component: alloc component_match without any comp to match Ramalingam C
2018-07-12 8:21 ` Daniel Vetter
2018-07-12 8:53 ` Ramalingam C
2018-07-11 14:11 ` [RFC 2/3] drm/i915: component master at i915 driver load Ramalingam C
2018-07-12 8:26 ` Daniel Vetter
2018-07-12 9:00 ` Ramalingam C
2018-07-11 14:11 ` [RFC 3/3] drm/i915: Initialize HDCP2.2 and its MEI interface Ramalingam C
2018-07-11 14:21 ` ✗ Fi.CI.BAT: failure for I915 component master Patchwork
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1531318288-23380-1-git-send-email-ramalingam.c@intel.com \
--to=ramalingam.c@intel.com \
--cc=alexander.usyskin@intel.com \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tomas.winkler@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox