From: Chris Wilson <chris@chris-wilson.co.uk>
To: Daniel Vetter <daniel@ffwll.ch>, "Sean Paul" <seanpaul@chromium.org>
Cc: seanpaul@google.com, "David Airlie" <airlied@linux.ie>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, daniel.vetter@intel.com
Subject: Re: [Intel-gfx] [PATCH v3 3/9] drm: Add Content Protection property
Date: Tue, 05 Dec 2017 15:40:47 +0000 [thread overview]
Message-ID: <151248844776.700.752575830165346316@mail.alporthouse.com> (raw)
In-Reply-To: <20171205153436.57efslvedeo63guu@phenom.ffwll.local>
Quoting Daniel Vetter (2017-12-05 15:34:36)
> Two bits missing imo:
> - Should explain that userspace should poll this property to detect a
> change from ENABLED to DESIRED (and take adequate actions and e.g. stop
> the stream). No uevent will be sent out because the HDCP specs require
> polling anyway.
What's more polling than poll()? :-p
-Chris
next prev parent reply other threads:[~2017-12-05 15:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 5:14 [PATCH v3 0/9] drm/i915: Implement HDCP Sean Paul
2017-12-05 5:15 ` [PATCH v3 1/9] drm: Fix link-status kerneldoc line lengths Sean Paul
2017-12-05 5:15 ` [PATCH v3 2/9] drm/i915: Add more control to wait_for routines Sean Paul
2017-12-05 17:13 ` Daniel Vetter
2017-12-05 23:09 ` [Intel-gfx] " Chris Wilson
2017-12-05 5:15 ` [PATCH v3 3/9] drm: Add Content Protection property Sean Paul
2017-12-05 8:07 ` Hans Verkuil
2017-12-05 15:27 ` [Intel-gfx] " Daniel Vetter
2017-12-05 15:34 ` Daniel Vetter
2017-12-05 15:40 ` Chris Wilson [this message]
2017-12-05 5:15 ` [PATCH v3 4/9] drm: Add some HDCP related #defines Sean Paul
2017-12-05 23:12 ` [Intel-gfx] " Chris Wilson
2017-12-06 15:01 ` Alex Deucher
2017-12-05 5:15 ` [PATCH v3 5/9] drm/i915: Add HDCP framework + base implementation Sean Paul
2017-12-05 9:06 ` Ramalingam C
2017-12-05 17:00 ` Daniel Vetter
2017-12-05 5:15 ` [PATCH v3 6/9] drm/i915: Make use of indexed write GMBUS feature Sean Paul
2017-12-05 17:01 ` [Intel-gfx] " Daniel Vetter
2017-12-05 17:33 ` Ville Syrjälä
2017-12-05 5:15 ` [PATCH v3 7/9] drm/i915: Add function to output Aksv over GMBUS Sean Paul
2017-12-05 17:02 ` [Intel-gfx] " Daniel Vetter
2017-12-05 5:15 ` [PATCH v3 8/9] drm/i915: Implement HDCP for HDMI Sean Paul
2017-12-05 17:06 ` Daniel Vetter
2017-12-05 5:15 ` [PATCH v3 9/9] drm/i915: Implement HDCP for DisplayPort Sean Paul
2017-12-05 14:30 ` Ramalingam C
2017-12-05 17:12 ` Daniel Vetter
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=151248844776.700.752575830165346316@mail.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=airlied@linux.ie \
--cc=daniel.vetter@intel.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seanpaul@chromium.org \
--cc=seanpaul@google.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).