[PATCH v7] unstable/drm-lease: DRM lease protocol support

[Philipp Zabel]

On Fri, 2019-10-18 at 08:51 +0000, Simon Ser wrote:
> On Thursday, October 17, 2019 11:15 PM, Drew DeVault <sir at cmpwn.com> wrote:
> 
> > On Thu Oct 17, 2019 at 6:08 PM Simon Ser wrote:
> > 
> > > Should we keep the connector event, now that we have an unprivileged
> > > DRM FD?
> > > Alternatives include:
> > > 
> > > -   Let the client use the FD to get what it needs (EDID/a configured
> > >     output/something else).
> > > 
> > 
> > Isn't this:
> > 
> > > -   Keep an event to advertise lease-able connector IDs
> > 
> > What it's still there for? I'm not sure I understand, otherwise how is
> > the client supposed to know which DRM resources it can request a lease
> > for? How does it encode those intentions into a lease request? afaict
> > the connector is still necessary.
> 
> The client can recognize EDIDs it's interested in, and then try to
> lease these connectors. The lease will fail if the connectors aren't
> leasable. This isn't a big deal for e.g. VR and we can always add the
> connector event later if needed.

If there was no event for the appearance of leasable connectors, the
client would have to listen to hotplug uevents itself if it wants to be
capable of handling HMDs plugged in later. Is this something we want to
require?

regards
Philipp