From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
Greg KH <gregkh@linuxfoundation.org>,
Takashi Iwai <tiwai@suse.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
Arnd Bergmann <arnd@arndb.de>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Sean Paul <sean@poorly.run>,
Maxime Ripard <maxime.ripard@bootlin.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Cc: dri-devel <dri-devel@lists.freedesktop.org>,
Dave Airlie <airlied@gmail.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
"DRM maintainer tools announcements, discussion,
and development" <dim-tools@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PULL] topic/component-typed
Date: Mon, 11 Feb 2019 18:15:20 +0100 [thread overview]
Message-ID: <CAKMK7uHU37VLbe4RBZ3GOow+=pupYAHotkVrpqJeiUcpSfjX8Q@mail.gmail.com> (raw)
Hi all,
Here's the typed component topic branch.
drm-intel maintainers: Please pull, I need this for the mei hdcp work from Ram.
drm-misc maintainers: Please pull, there's a drm doc patch follow-up
that I want to stuff into drm-misc-next.
Greg: The drm side missed our feature cutoff, so will only land in 5.2.
Probably good if you pull this into drivers-core so it lands a bit
quicker. You&Arnd will also get a topic pull later on with the MEI bits
for char-misc tree, which needs to be based on top of this tree here.
Takashi: Since the drm side only lands in 5.2 might be good if you
pull this in too to avoid conflicts.
Cheers, Daniel
topic/component-typed-2019-02-11:
typed componented support + i915/snd-hda changes
This is needed by the new MEI-HDCP support in i915, so will need to go
in through drm and drivers-misc trees at least.
Cheers, Daniel
The following changes since commit 8834f5600cf3c8db365e18a3d5cac2c2780c81e5:
Linux 5.0-rc5 (2019-02-03 13:48:04 -0800)
are available in the Git repository at:
git://anongit.freedesktop.org/drm/drm-intel
tags/topic/component-typed-2019-02-11
for you to fetch changes up to 8857c7d065e900a0b3829c97634c99501b606541:
i915/snd_hdac: I915 subcomponent for the snd_hdac (2019-02-08 16:58:59 +0100)
----------------------------------------------------------------
typed componented support + i915/snd-hda changes
This is needed by the new MEI-HDCP support in i915, so will need to go
in through drm and drivers-misc trees at least.
----------------------------------------------------------------
Daniel Vetter (3):
component: Add documentation
components: multiple components for a device
i915/snd_hdac: I915 subcomponent for the snd_hdac
Documentation/driver-api/component.rst | 17 +++
Documentation/driver-api/device_link.rst | 3 +
Documentation/driver-api/index.rst | 1 +
drivers/base/component.c | 206 +++++++++++++++++++++++++++++--
drivers/gpu/drm/i915/intel_audio.c | 4 +-
include/drm/i915_component.h | 4 +
include/linux/component.h | 76 ++++++++++++
include/sound/hda_component.h | 5 +-
sound/hda/hdac_component.c | 4 +-
sound/hda/hdac_i915.c | 6 +-
10 files changed, 308 insertions(+), 18 deletions(-)
create mode 100644 Documentation/driver-api/component.rst
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
next reply other threads:[~2019-02-11 17:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 17:15 Daniel Vetter [this message]
2019-02-11 18:25 ` [PULL] topic/component-typed Sam Ravnborg
2019-02-11 18:50 ` Daniel Vetter
2019-02-11 18:57 ` Takashi Iwai
2019-02-11 19:18 ` Daniel Vetter
2019-02-11 19:34 ` Greg KH
2019-02-12 9:24 ` Maxime Ripard
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='CAKMK7uHU37VLbe4RBZ3GOow+=pupYAHotkVrpqJeiUcpSfjX8Q@mail.gmail.com' \
--to=daniel.vetter@ffwll.ch \
--cc=airlied@gmail.com \
--cc=arnd@arndb.de \
--cc=dim-tools@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=maxime.ripard@bootlin.com \
--cc=rodrigo.vivi@intel.com \
--cc=sean@poorly.run \
--cc=tiwai@suse.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;
as well as URLs for NNTP newsgroup(s).