systemd/rules.d/60-persistent-media-controller.rules

# do not edit this file, it will be overwritten on update

# Media controller rules

ACTION=="remove", GOTO="persistent_media_ctl_end"
SUBSYSTEM!="media", GOTO="persistent_media_ctl_end"
ENV{MAJOR}=="", GOTO="persistent_media_ctl_end"

IMPORT{builtin}="path_id"
KERNEL=="media*", ENV{ID_PATH_WITH_USB_REVISION}=="?*", SYMLINK+="media/by-path/$env{ID_PATH_WITH_USB_REVISION}-media-controller"
KERNEL=="media*", ENV{ID_PATH_WITH_USB_REVISION}=="", ENV{ID_PATH}=="?*", SYMLINK+="media/by-path/$env{ID_PATH}-media-controller"

LABEL="persistent_media_ctl_end"
udev: Add /dev/media/by-path symlinks for media controllers Add persistent symlinks for media controller ("mediaX") devices, based on their ID_PATH udev properties. For example, if the uvcvideo driver creates /dev/media0, a persistent name may be: /dev/media/by-path/pci-0000:04:00.3-usb-0:1:1.0-media-controller Persistent links are a handy tool to make scripts self-documenting during development or in tests, as well as less error prone in case of devices changing enumeration order. For media controllers, one can alternatively scan through all of them and look for a matching bus_info in their struct media_device_info, but the links are much handier when drafting something by hand. A similar pattern already exists for Video4Linux /dev/videoX devices, see 60-persistent-v4l.rules for those. 2024-02-22 11:47:36 +03:00			`# do not edit this file, it will be overwritten on update`

			`# Media controller rules`

			`ACTION=="remove", GOTO="persistent_media_ctl_end"`
			`SUBSYSTEM!="media", GOTO="persistent_media_ctl_end"`
			`ENV{MAJOR}=="", GOTO="persistent_media_ctl_end"`

			`IMPORT{builtin}="path_id"`
udev: permanent symlinks with USB revision for /dev/media* As a follow-up in the style of: 873be895ed ("udev: add USB revision in ID_PATH") this patch adds a second symlink for media controllers, this time including the USB revision. This means that in addition to persistent symlinks like: pci-0000:04:00.3-usb-0:1:1.0-media-controller -> ../../media0 We now also get: pci-0000:04:00.3-usbv2-0:1:1.0-media-controller -> ../../media0 ...which helps distinguish media devices plugged into different USB root hubs provided by the same PCI card, at least as long as they are for different USB revisions. Fixes: 04f19d6735 ("udev: Add /dev/media/by-path symlinks for media controllers") 2024-04-17 09:30:44 +03:00			`KERNEL=="media", ENV{ID_PATH_WITH_USB_REVISION}=="?", SYMLINK+="media/by-path/$env{ID_PATH_WITH_USB_REVISION}-media-controller"`
			`KERNEL=="media", ENV{ID_PATH_WITH_USB_REVISION}=="", ENV{ID_PATH}=="?", SYMLINK+="media/by-path/$env{ID_PATH}-media-controller"`
udev: Add /dev/media/by-path symlinks for media controllers Add persistent symlinks for media controller ("mediaX") devices, based on their ID_PATH udev properties. For example, if the uvcvideo driver creates /dev/media0, a persistent name may be: /dev/media/by-path/pci-0000:04:00.3-usb-0:1:1.0-media-controller Persistent links are a handy tool to make scripts self-documenting during development or in tests, as well as less error prone in case of devices changing enumeration order. For media controllers, one can alternatively scan through all of them and look for a matching bus_info in their struct media_device_info, but the links are much handier when drafting something by hand. A similar pattern already exists for Video4Linux /dev/videoX devices, see 60-persistent-v4l.rules for those. 2024-02-22 11:47:36 +03:00
			`LABEL="persistent_media_ctl_end"`