New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 923165 link

Starred by 1 user

Issue metadata

Status: Unconfirmed
Owner:
Last visit > 30 days ago
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Feature
Gfx



Sign in to add a comment

Displaylink 3.0 devices should have proper parent in sysfs

Project Member Reported by dtor@google.com, Jan 17 (5 days ago)

Issue description

Currently Displaylink devices using evdi subsystem live in /sys/devices/platform/evdi.N/...

This is not helpful if they are multi-function devices (such as external display with touchscreen connected via USB), as we need to associate the display and the touchscreen and one of the ways would be to use common sysfs hierarchy (such as both devices connected to the same USB HUB).

An option is to pass path to the parent (such as USB interface) as argument when writing into "add" attribute of evdi and have kernel traverse proper bus and locate device with given path, then use it as the parent of evdi device.
 

Comment 1 by kdgwill@chromium.org, Jan 18 (5 days ago)

Cc: ziegs@chromium.org kdgwill@chromium.org

Comment 2 by marcheu@google.com, Jan 18 (5 days ago)

Cc: displaylink@chromium.org
Labels: Gfx
@displaylink team, we would like to have the same pairing which is possible on udl but with evdi. Do you think that's doable? Intuitively, we could have a private API where dlm reports its usb device to the kernel and the kernel reparents it.

Sign in to add a comment