Unfortunately there doesn't seem to be a way for to write a udev rule
against a pseudo terminal...
On 3/8/24 11:31, Aleksander Morgado wrote:
Hey Garfield,
I have a situation where I have a ublox modem, the LISA u200, wired up using
its SPI bus as the communication channel. On the DTE side is a raspberry pi SBC
with a custom spi platform driver that exposes a tty device for modem. This
driver is not capable of multiplexing and exposing multiple virtual channels.
To overcome this I have a user mode daemon that performs this function by
connection to the single tty port exposed by the spi driver and in turn creating 5
pseudo tty's (/dev/ptty1 -> /dev/ptty5) to interact with. These are actually
links to /dev/pts/1 to /dev/pts/5.
I want the ublox plugin to manage this device but there seems to be no way to
filter/grab those ports.
You should be able to add the ID_MM_PHYSDEV_UID udev tags for all
those pseudo TTYs, so that ModemManager can "bind" all those ports
together to the same modem object, see
https://www.freedesktop.org/software/ModemManager/doc/latest/ModemManager/ModemManager-Common-udev-tags.html#ID-MM-PHYSDEV-UID:CAPS
