($INBOX_DIR/description missing)
 help / color / mirror / Atom feed
From: Adam Pigg <adam@piggz.co.uk>
To: ofono@lists.linux.dev
Subject: USB Hub resets - EG25 / Pinephone Pro
Date: Wed, 10 May 2023 16:32:22 +0100	[thread overview]
Message-ID: <3234634.44csPzL39Z@adam-laptop-hp> (raw)

Hi

Im just really seeking some ideas on how to handle the modem in the pinephone 
pro.

Initially, all is good, and the modem works, however, after enabling power 
management and allowing the phone to suspend/resume, ive hit a problem where 
on resume, the usb hun the modem is connected to resets.  This causes the 
modem to dissapear/reappear.

When it re-appears, my debugging has found that devices probed initially are 
now not present (a usbmisc and wwan device), however, the 3 modem tty devices 
are there. See below from some debug logs

This causes the ofono plugin to not register a device (the wwan device is 
required for this), which isnt ideal on a mobile phone.

Any ideas are welcomed on how to handle this.

Kind Regards

Adam Pigg




    On Boot:
    May 08 18:14:10 PinePhonePro ofonod[353]: plugins/udevng.c:create_modem() 
/sys/devices/platform/fe3c0000.usb/usb1/1-1
    May 08 18:14:10 PinePhonePro ofonod[353]: plugins/udevng.c:create_modem() 
driver=quectelqmi
    May 08 18:14:10 PinePhonePro ofonod[353]: src/modem.c:ofono_modem_create() 
name: (null), type: quectelqmi
    May 08 18:14:10 PinePhonePro ofonod[353]: plugins/
udevng.c:setup_quectelqmi() /sys/devices/platform/fe3c0000.usb/usb1/1-1
    May 08 18:14:10 PinePhonePro ofonod[353]: plugins/
udevng.c:setup_quectelqmi() /dev/ttyUSB0 255/255/255 00 (null) tty
    May 08 18:14:10 PinePhonePro ofonod[353]: plugins/
udevng.c:setup_quectelqmi() /dev/ttyUSB1 255/0/0 01 (null) tty
    May 08 18:14:10 PinePhonePro ofonod[353]: plugins/
udevng.c:setup_quectelqmi() /dev/ttyUSB2 255/0/0 02 (null) tty
    May 08 18:14:10 PinePhonePro ofonod[353]: plugins/
udevng.c:setup_quectelqmi() /dev/ttyUSB3 255/0/0 03 (null) tty
    May 08 18:14:10 PinePhonePro ofonod[353]: plugins/
udevng.c:setup_quectelqmi() /dev/cdc-wdm0 255/255/255 04 (null) usbmisc
    May 08 18:14:10 PinePhonePro ofonod[353]: plugins/
udevng.c:setup_quectelqmi() wwan0 255/255/255 04 (null) net
    May 08 18:14:10 PinePhonePro ofonod[353]: plugins/
udevng.c:setup_quectelqmi() qmi=/dev/cdc-wdm0 net=wwan0
    May 08 18:14:10 PinePhonePro ofonod[353]: plugins/
udevng.c:setup_quectelqmi() qmi=/dev/cdc-wdm0 net=wwan0
    ​
    ​
    On Resume:
    May 08 18:15:05 PinePhonePro ofonod[353]: plugins/
udevng.c:setup_quectelqmi() /sys/devices/platform/fe3c0000.usb/usb1/1-1
    May 08 18:15:05 PinePhonePro ofonod[353]: plugins/
udevng.c:setup_quectelqmi() /dev/ttyUSB0 255/255/255 00 (null) tty
    May 08 18:15:05 PinePhonePro ofonod[353]: plugins/
udevng.c:setup_quectelqmi() /dev/ttyUSB1 255/0/0 01 (null) tty
    May 08 18:15:05 PinePhonePro ofonod[353]: plugins/
udevng.c:setup_quectelqmi() /dev/ttyUSB2 255/0/0 02 (null) tty
    May 08 18:15:05 PinePhonePro ofonod[353]: plugins/
udevng.c:setup_quectelqmi() /dev/ttyUSB3 255/0/0 03 (null) tty
    May 08 18:15:05 PinePhonePro ofonod[353]: plugins/
udevng.c:setup_quectelqmi() qmi=(null) net=(null)
    ​




                 reply	other threads:[~2023-05-10 15:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3234634.44csPzL39Z@adam-laptop-hp \
    --to=adam@piggz.co.uk \
    --cc=ofono@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).