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

[Simon Ser]

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.

Regarding the second point: the current event creates an object, which
makes the protocol complicated with e.g. the stop request. We could
just have a connector event which sends a uint connector_id without
creating a new object.