Modem creation/startup order

Colin Helliwell colin.helliwell at
Wed Feb 15 15:16:04 UTC 2017

> On 15 February 2017 at 15:07 Colin Helliwell <colin.helliwell at> wrote:
> > On 15 February 2017 at 14:11 Aleksander Morgado <aleksander at> wrote:
> > 
> > Is the logic stopping there? the ID_MM_PHYSDEV_UID should take
> > precedence to whatever parent sysfs path is set, e.g. you could set
> > each tty's own sysfs path as parent sysfs path and would (should)
> > still work.
> On that assumption, I've been working through the code and can see that mm_kernel_device_get_physdev_uid() [which points to the udev kernel_device_get_physdev_uid()] is indeed called by device_added(), but *after* mm_kernel_device_is_candidate() is called [which points to the udev kernel_device_is_candidate()], and which 'errors' with the above message from line 458. I think!

Not sure of the intended purpose of ID_MM_PHYSDEV_UID but, if it's there as an override, would it be acceptable to allow its presence to override the 
    if (!self->priv->physdev) {
in kernel_device_is_candidate() ?

More information about the ModemManager-devel mailing list