All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Clark <robdclark@gmail.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 2/2] drm: Add Content Protection Desired property to drm
Date: Thu, 4 Dec 2014 10:47:25 -0500	[thread overview]
Message-ID: <CAF6AEGsEHu6kudEbarHu5a70+-2kSpPjr0UT=1bVyXcv88F72Q@mail.gmail.com> (raw)
In-Reply-To: <20141204100310.GH32117@phenom.ffwll.local>

On Thu, Dec 4, 2014 at 5:03 AM, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Wed, Dec 03, 2014 at 11:31:47PM +0200, Ville Syrjälä wrote:
>> On Wed, Dec 03, 2014 at 11:57:41AM -0800, Sean Paul wrote:
>> > Add a new standard connector property to track whether content protection
>> > (ex: hdcp) is desired by userspace. While there are 3 possible states for the
>> > property, userspace should only change the value to desired or undesired.
>> > Upon setting the value to desired, the driver is responsible for protecting
>> > the link and setting the value to enabled. Disabling protection should happen
>> > immediately.
>>
>> Having a magic part r/w part r/o property doesn't sound very appealing
>> to me. I'm thinking it would be cleaner to just have two properties for
>> such things.
>
> Yeah I think we should have a separate property which displays the current
> sink key/id to indicate to userspace whether hdcp is established and to
> what sink it's locked.
>
> And we should have an upstream implementation to review, not just the doc
> update, too.

Since we are starting to get patches for driver support for HDCP, I'd
asked Sean to send this patch to get the process going on what we want
the interface to look like.  It is fine to defer merging until we have
driver bits to go along with it, but either way I think now is a good
time to sort out what we want it to look like from userspace

BR,
-R


> -Daniel
> --
> Daniel Vetter
> Software Engineer, Intel Corporation
> +41 (0) 79 365 57 48 - http://blog.ffwll.ch
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dri-devel
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2014-12-04 15:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-03 19:57 [PATCH 1/2] drm/Documentation: Fix rowspan value in drm-kms-properties Sean Paul
2014-12-03 19:57 ` [PATCH 2/2] drm: Add Content Protection Desired property to drm Sean Paul
2014-12-03 21:31   ` Ville Syrjälä
2014-12-04 10:03     ` Daniel Vetter
2014-12-04 15:47       ` Rob Clark [this message]
2014-12-04 19:03       ` [PATCH v2 2/2] drm: Add Content Protection properties " Sean Paul
2016-12-20 18:36         ` Daniel Vetter
2014-12-04 10:03 ` [PATCH 1/2] drm/Documentation: Fix rowspan value in drm-kms-properties 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='CAF6AEGsEHu6kudEbarHu5a70+-2kSpPjr0UT=1bVyXcv88F72Q@mail.gmail.com' \
    --to=robdclark@gmail.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@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 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.