Aliases for DRI connectors?

Matt Hoosier matt.hoosier at gmail.com
Wed Apr 1 21:25:19 UTC 2020


On Wed, Apr 1, 2020 at 3:17 PM Simon Ser <contact at emersion.fr> wrote:

> On Wednesday, April 1, 2020 9:38 PM, Matt Hoosier <matt.hoosier at gmail.com>
> wrote:
>
> > I'm searching for some sort of scheme that will let my DRI master query
> the set of available connectors and select the one carrying a prearranged
> designation. The problem I'm trying to solve is to allow deploying one
> standardized userspace component across a fleet of devices that have
> varying numbers of displays, with the use cases not always driven on the
> same connector topologically.
> >
> > I had a look around the properties available on my system's DRI
> connectors, and nothing immediate jumped out at me. Is there a standard
> connector property that (assuming I can find the right place in DeviceTree
> or similar to) that would be a good fit for this?
>
> Maybe information in the EDID would help? You'll find the manufacturer,
> the model number and the serial number.
>

That might be a possibility. The trouble there is that there can be more
than one instance of the same display model connected to the system, so the
EDID blob wouldn't be particularly helpful to distinguish them. The
connectors in question are generally something like LVDS or DSI that don't
typically expose EDID properties, too.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20200401/0a12a493/attachment.htm>


More information about the dri-devel mailing list