All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: Greg KH <gregkh@linuxfoundation.org>,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	Arnd Bergmann <arnd@arndb.de>
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
	dim-tools@lists.freedesktop.org,
	LKML <linux-kernel@vger.kernel.org>
Subject: [PULL] topic/mei-hdcp
Date: Tue, 19 Feb 2019 08:55:27 +0100	[thread overview]
Message-ID: <20190219071619.GA11016@phenom.ffwll.local> (raw)

Hi all,

topic/mei-hdcp-2019-02-19:
Prep patches + headers for the mei-hdcp/i915 component interfaces

Also contains the prep work in the component helpers plus adjustements
for the snd-hda/i915 component interface.

Plus one small static inline in the drm_hdcp.h header that both i915
and mei_hdcp will need.

Joonas, please pull into drm-intel-next-queued so I can apply the i915
hdcp patches.

Greg/Arnd, I think there's two options to get the mei-hdcp patches landed
into drivers-misc:
- You pull this topic pull and then apply the mei-hdcp patches on top in
  char-misc-next.
- I also pull in char-misc-next to get at 32ea33a04484 ("mei: bus: export
  to_mei_cl_device for mei client devices drivers") and then apply all the
  mei-hdcp stuff into a new topic branch.

I think 2nd option would be better, allows us to integration test easier,
and we'll have a topic branch in case we need a fixup spanning mei-hdcp
and i915. Also would allow me to start merging the patches, since I think
it's too late for 5.1.

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/mei-hdcp-2019-02-19

for you to fetch changes up to 35c0272502cca0a1b461d310c23aac94a503983d:

  drm/audio: declaration of struct device (2019-02-18 20:19:28 +0100)

----------------------------------------------------------------
Prep patches + headers for the mei-hdcp/i915 component interfaces

Also contains the prep work in the component helpers plus adjustements
for the snd-hda/i915 component interface.

Plus one small static inline in the drm_hdcp.h header that both i915
and mei_hdcp will need.

----------------------------------------------------------------
Daniel Vetter (3):
      component: Add documentation
      components: multiple components for a device
      i915/snd_hdac: I915 subcomponent for the snd_hdac

Ramalingam C (5):
      drm/i915: enum port definition is moved into i915_drm.h
      drm/i915: header for i915 - MEI_HDCP interface
      drm/i915: MEI interface definition
      drm: helper functions for hdcp2 seq_num to from u32
      drm/audio: declaration of struct device

 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 +-
 drivers/gpu/drm/i915/intel_display.h     |  16 +--
 include/drm/drm_audio_component.h        |   1 +
 include/drm/drm_hdcp.h                   |  18 +++
 include/drm/i915_component.h             |   5 +
 include/drm/i915_drm.h                   |  15 +++
 include/drm/i915_mei_hdcp_interface.h    | 149 ++++++++++++++++++++++
 include/linux/component.h                |  76 ++++++++++++
 include/sound/hda_component.h            |   5 +-
 sound/hda/hdac_component.c               |   4 +-
 sound/hda/hdac_i915.c                    |   6 +-
 15 files changed, 493 insertions(+), 33 deletions(-)
 create mode 100644 Documentation/driver-api/component.rst
 create mode 100644 include/drm/i915_mei_hdcp_interface.h

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch

WARNING: multiple messages have this Message-ID (diff)
From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: Greg KH <gregkh@linuxfoundation.org>, Arnd Bergmann <arnd@arndb.de>
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
	dim-tools@lists.freedesktop.org,
	LKML <linux-kernel@vger.kernel.org>
Subject: [PULL] topic/mei-hdcp
Date: Tue, 19 Feb 2019 08:55:27 +0100	[thread overview]
Message-ID: <20190219071619.GA11016@phenom.ffwll.local> (raw)

Hi all,

topic/mei-hdcp-2019-02-19:
Prep patches + headers for the mei-hdcp/i915 component interfaces

Also contains the prep work in the component helpers plus adjustements
for the snd-hda/i915 component interface.

Plus one small static inline in the drm_hdcp.h header that both i915
and mei_hdcp will need.

Joonas, please pull into drm-intel-next-queued so I can apply the i915
hdcp patches.

Greg/Arnd, I think there's two options to get the mei-hdcp patches landed
into drivers-misc:
- You pull this topic pull and then apply the mei-hdcp patches on top in
  char-misc-next.
- I also pull in char-misc-next to get at 32ea33a04484 ("mei: bus: export
  to_mei_cl_device for mei client devices drivers") and then apply all the
  mei-hdcp stuff into a new topic branch.

I think 2nd option would be better, allows us to integration test easier,
and we'll have a topic branch in case we need a fixup spanning mei-hdcp
and i915. Also would allow me to start merging the patches, since I think
it's too late for 5.1.

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/mei-hdcp-2019-02-19

for you to fetch changes up to 35c0272502cca0a1b461d310c23aac94a503983d:

  drm/audio: declaration of struct device (2019-02-18 20:19:28 +0100)

----------------------------------------------------------------
Prep patches + headers for the mei-hdcp/i915 component interfaces

Also contains the prep work in the component helpers plus adjustements
for the snd-hda/i915 component interface.

Plus one small static inline in the drm_hdcp.h header that both i915
and mei_hdcp will need.

----------------------------------------------------------------
Daniel Vetter (3):
      component: Add documentation
      components: multiple components for a device
      i915/snd_hdac: I915 subcomponent for the snd_hdac

Ramalingam C (5):
      drm/i915: enum port definition is moved into i915_drm.h
      drm/i915: header for i915 - MEI_HDCP interface
      drm/i915: MEI interface definition
      drm: helper functions for hdcp2 seq_num to from u32
      drm/audio: declaration of struct device

 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 +-
 drivers/gpu/drm/i915/intel_display.h     |  16 +--
 include/drm/drm_audio_component.h        |   1 +
 include/drm/drm_hdcp.h                   |  18 +++
 include/drm/i915_component.h             |   5 +
 include/drm/i915_drm.h                   |  15 +++
 include/drm/i915_mei_hdcp_interface.h    | 149 ++++++++++++++++++++++
 include/linux/component.h                |  76 ++++++++++++
 include/sound/hda_component.h            |   5 +-
 sound/hda/hdac_component.c               |   4 +-
 sound/hda/hdac_i915.c                    |   6 +-
 15 files changed, 493 insertions(+), 33 deletions(-)
 create mode 100644 Documentation/driver-api/component.rst
 create mode 100644 include/drm/i915_mei_hdcp_interface.h

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch

             reply	other threads:[~2019-02-19  7:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-19  7:55 Daniel Vetter [this message]
2019-02-19  7:55 ` [PULL] topic/mei-hdcp Daniel Vetter
2019-02-19 12:35 ` Greg KH
2019-02-19 12:35   ` Greg KH
2019-02-20 10:04 ` Joonas Lahtinen

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=20190219071619.GA11016@phenom.ffwll.local \
    --to=daniel.vetter@ffwll.ch \
    --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=rodrigo.vivi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.