mbim-proxy listening to systemd suspend/resume events
gciofono at gmail.com
Sat Sep 19 08:41:04 UTC 2020
> I also thought about the udev tags as the last option. Before
> resorting to that, though, we could attempt to detect the state of the
> modem after a suspend/resume cycle. E.g. just upon resume, we attempt
> to contact the modem using the control channels that we had open, and
> if they work we check the status of the connection if it was up before
> the suspend. And if the modem doesn't reply at all, we directly assume
> we need to mark the modem object as invalid and reprobe from scratch.
> Don't know, something like that; I'm sure there will be corner cases
> to handle in the different devices, but at least that could give us a
> good start.
it doesn't seem very elegant to crash the modem once to avoid crashing it
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the libmbim-devel