* [PULL] topic/mei-hdcp
@ 2019-02-19 7:55 ` Daniel Vetter
0 siblings, 0 replies; 5+ messages in thread
From: Daniel Vetter @ 2019-02-19 7:55 UTC (permalink / raw)
To: Greg KH, Joonas Lahtinen, Arnd Bergmann
Cc: Jani Nikula, Joonas Lahtinen, Rodrigo Vivi, dri-devel, intel-gfx,
dim-tools, LKML
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
^ permalink raw reply [flat|nested] 5+ messages in thread* [PULL] topic/mei-hdcp
@ 2019-02-19 7:55 ` Daniel Vetter
0 siblings, 0 replies; 5+ messages in thread
From: Daniel Vetter @ 2019-02-19 7:55 UTC (permalink / raw)
To: Greg KH, Arnd Bergmann
Cc: Jani Nikula, Joonas Lahtinen, Rodrigo Vivi, dri-devel, intel-gfx,
dim-tools, LKML
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
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [PULL] topic/mei-hdcp
2019-02-19 7:55 ` Daniel Vetter
@ 2019-02-19 12:35 ` Greg KH
-1 siblings, 0 replies; 5+ messages in thread
From: Greg KH @ 2019-02-19 12:35 UTC (permalink / raw)
To: Joonas Lahtinen, Arnd Bergmann, Jani Nikula, Rodrigo Vivi,
dri-devel, intel-gfx, dim-tools, LKML
On Tue, Feb 19, 2019 at 08:55:27AM +0100, Daniel Vetter wrote:
> 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.
No objection from me, pull away!
greg k-h
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [PULL] topic/mei-hdcp
@ 2019-02-19 12:35 ` Greg KH
0 siblings, 0 replies; 5+ messages in thread
From: Greg KH @ 2019-02-19 12:35 UTC (permalink / raw)
To: Joonas Lahtinen, Arnd Bergmann, Jani Nikula, Rodrigo Vivi,
dri-devel, intel-gfx, dim-tools, LKML
On Tue, Feb 19, 2019 at 08:55:27AM +0100, Daniel Vetter wrote:
> 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.
No objection from me, pull away!
greg k-h
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PULL] topic/mei-hdcp
2019-02-19 7:55 ` Daniel Vetter
(?)
(?)
@ 2019-02-20 10:04 ` Joonas Lahtinen
-1 siblings, 0 replies; 5+ messages in thread
From: Joonas Lahtinen @ 2019-02-20 10:04 UTC (permalink / raw)
To: Arnd Bergmann, Daniel Vetter, Greg KH
Cc: Jani Nikula, Rodrigo Vivi, dri-devel, intel-gfx, dim-tools, LKML
Quoting Daniel Vetter (2019-02-19 09:55:27)
> 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.
This is now pulled.
Regards, Joonas
>
> 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
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2019-02-20 10:04 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-02-19 7:55 [PULL] topic/mei-hdcp Daniel Vetter
2019-02-19 7:55 ` Daniel Vetter
2019-02-19 12:35 ` Greg KH
2019-02-19 12:35 ` Greg KH
2019-02-20 10:04 ` Joonas Lahtinen
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.