aboutsummaryrefslogtreecommitdiff
path: root/src/mm-port-serial.c
diff options
context:
space:
mode:
authorAleksander Morgado <aleksander@aleksander.es>2017-03-06 12:01:56 +0100
committerAleksander Morgado <aleksander@aleksander.es>2017-03-22 09:40:10 +0100
commit00fb9e98f6003f6b167f7d12a895ec3d1402b027 (patch)
treed1fc5df50bfec704fb257bb7dc8091fe64163eb9 /src/mm-port-serial.c
parent230e732a24e0e925f535839caecc4a69d89ab89e (diff)
kernel-device: device-specific properties in either port or physdev
There are 2 main types of udev properties: device-specific and port-specific. The port-specific properties are set independently per port (e.g. port type hints set per interface number for a given vid:pid). The device-specific properties apply to all ports in the device. Some of these properties are currently expected in the physical device (e.g. ID_MM_PLATFORM_DRIVER_PROBE) while some others are expected in each port (e.g. the plugin udev tag filters). This patch tries to simplify the logic and just assume that the device specific tags may be given in either the physical device or the port device, by providing separate APIs to retrieve port-specific or device-specific (global) properties. If the same tag is given in both the device and the port, the one in the device takes preference. For the generic backend, these new APIs are really useless, as all device-specific and port-specific properties are always stored in the port object themselves (there is no 'tree' of devices in the generic backend, no 'physdev' device). For the udev backend, though, there really is a difference, as the tags may be set in port or device. https://bugs.freedesktop.org/show_bug.cgi?id=100156
Diffstat (limited to 'src/mm-port-serial.c')
0 files changed, 0 insertions, 0 deletions