From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [RFC PATCH 0/6] drm/i915: Implement HDCP
Date: Tue, 5 Dec 2017 15:45:45 +0200 [thread overview]
Message-ID: <20171205134545.GU10981@intel.com> (raw)
In-Reply-To: <20171130075038.5rv6vywzeeeayhyq@phenom.ffwll.local>
On Thu, Nov 30, 2017 at 08:50:38AM +0100, Daniel Vetter wrote:
> On Wed, Nov 29, 2017 at 10:08:55PM -0500, Sean Paul wrote:
> > Here's the RFC for my i915 HDCP patchset. The UABI is based on what we've been
> > using in Chrome for the past 3 years. I posted the property to the list back
> > then, but never had a mainline driver to implement it. I do now :-)
> >
> > Things are mostly in place, danvet gave me some feedback that I will
> > incorporate in v1. However, in the interest of gaining more early feedback, I'm
> > posting this now.
> >
> > TODO:
> > - Add kerneldoc for property
>
> The big thing I'd like to see here is clear description of the flows
> between kernel and userspace (since there's no helpers on the kernel side
> to standardize this).
>
> One thing we discussed in that context is the addition of an uevent (like
> we do for anything else that changes with connectors, link_status is one
> example). But since the hdcp spec explicitly demands that the video player
> must poll the status an event is moot and won't be used. And I'm no fan of
> speculative uapi :-)
Speaking of uapi... Do we have an open source userspace and igts for
this somewhere?
I'm also concerned about debugging this. It will be a real PITA
to do if we can't even test it easily.
>
> > - Fix '//' comments
> > - Change to MIT license
> > - Rebase on Ville's gmbus fixes (thanks Ville)
> > - Improve documentation on drm_intel_hdcp_shim
> > - Fix async commit locking (ie: don't use connection_mutex)
> > - Don't change connector->state in enable, defer to worker
>
> Same holds for the disable callback, you can't touch state in there.
>
> With the link_status prop (which is somewhat similar) we only reset it in
> atomic_check (where we hold the state locks) and in the async worker (same
> applies).
> -Daniel
>
> > - Add igt coverage for the feature.
> >
> > Thanks!
> >
> > Sean
> >
> >
> > Sean Paul (6):
> > drm: Add Content Protection property
> > drm: Add some HDCP related #defines
> > drm/i915: Add HDCP framework + base implementation
> > drm/i915: Add function to output Aksv over GMBUS
> > drm/i915: Implement HDCP for HDMI
> > drm/i915: Implement HDCP for DisplayPort
> >
> > drivers/gpu/drm/drm_atomic.c | 8 +
> > drivers/gpu/drm/drm_connector.c | 43 +++
> > drivers/gpu/drm/drm_sysfs.c | 29 ++
> > drivers/gpu/drm/i915/Makefile | 1 +
> > drivers/gpu/drm/i915/i915_drv.h | 1 +
> > drivers/gpu/drm/i915/i915_reg.h | 85 +++++
> > drivers/gpu/drm/i915/intel_atomic.c | 26 +-
> > drivers/gpu/drm/i915/intel_ddi.c | 64 ++++
> > drivers/gpu/drm/i915/intel_dp.c | 243 +++++++++++++-
> > drivers/gpu/drm/i915/intel_drv.h | 53 +++
> > drivers/gpu/drm/i915/intel_hdcp.c | 636 ++++++++++++++++++++++++++++++++++++
> > drivers/gpu/drm/i915/intel_hdmi.c | 253 ++++++++++++++
> > drivers/gpu/drm/i915/intel_i2c.c | 54 ++-
> > include/drm/drm_connector.h | 16 +
> > include/drm/drm_dp_helper.h | 17 +
> > include/drm/drm_hdcp.h | 44 +++
> > include/uapi/drm/drm_mode.h | 4 +
> > 17 files changed, 1560 insertions(+), 17 deletions(-)
> > create mode 100644 drivers/gpu/drm/i915/intel_hdcp.c
> > create mode 100644 include/drm/drm_hdcp.h
> >
> > --
> > 2.15.0.531.g2ccb3012c9-goog
> >
> > _______________________________________________
> > Intel-gfx mailing list
> > Intel-gfx@lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/intel-gfx
>
> --
> Daniel Vetter
> Software Engineer, Intel Corporation
> http://blog.ffwll.ch
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Ville Syrjälä
Intel OTC
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-12-05 13:45 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 3:08 [RFC PATCH 0/6] drm/i915: Implement HDCP Sean Paul
2017-11-30 3:08 ` [RFC PATCH 1/6] drm: Add Content Protection property Sean Paul
2017-12-05 10:28 ` Pavel Machek
2017-12-05 10:45 ` Daniel Vetter
2017-12-05 17:34 ` Pavel Machek
2017-12-05 17:53 ` Alex Deucher
2017-12-05 18:01 ` Pavel Machek
[not found] ` <CADnq5_PcbBeGL+3CxOpNgRiih4czU9SnmjNbRyyRHOn-OZvy5Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-12-07 14:32 ` Alan Cox
2017-12-05 19:03 ` Sean Paul
2017-12-05 20:14 ` Daniel Stone
2017-12-07 14:30 ` Alan Cox
2017-12-08 8:55 ` Daniel Vetter
2017-11-30 3:08 ` [RFC PATCH 2/6] drm: Add some HDCP related #defines Sean Paul
2017-11-30 3:08 ` [RFC PATCH 3/6] drm/i915: Add HDCP framework + base implementation Sean Paul
2017-11-30 9:12 ` [Intel-gfx] " Chris Wilson
2017-12-01 7:23 ` Ramalingam C
2017-12-01 7:36 ` Daniel Vetter
2017-12-01 8:36 ` [Intel-gfx] " Ramalingam C
2017-12-01 14:13 ` Sean Paul
2017-12-01 14:12 ` [Intel-gfx] " Sean Paul
2017-12-01 14:16 ` Sean Paul
2017-11-30 3:08 ` [RFC PATCH 4/6] drm/i915: Add function to output Aksv over GMBUS Sean Paul
2017-11-30 3:09 ` [RFC PATCH 5/6] drm/i915: Implement HDCP for HDMI Sean Paul
2017-12-01 7:31 ` Ramalingam C
2017-11-30 3:09 ` [RFC PATCH 6/6] drm/i915: Implement HDCP for DisplayPort Sean Paul
2017-11-30 7:50 ` [Intel-gfx] [RFC PATCH 0/6] drm/i915: Implement HDCP Daniel Vetter
2017-12-05 13:45 ` Ville Syrjälä [this message]
2017-12-05 14:45 ` Sean Paul
2017-11-30 9:07 ` ✗ Fi.CI.BAT: failure for " Patchwork
2017-11-30 10:05 ` Patchwork
2017-11-30 15:15 ` 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=20171205134545.GU10981@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
/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