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