Hi, * Johan Hovold <johan@xxxxxxxxxx> [200528 13:07]: > On Tue, May 12, 2020 at 02:47:12PM -0700, Tony Lindgren wrote: > > +/* > > + * Motorola MDM GNSS device communicates over a dedicated TS 27.010 channel > > + * using custom data packets. The packets look like AT commands embedded into > > + * a Motorola invented packet using format like "U1234AT+MPDSTART=0,1,100,0". > > + * But it's not an AT compatible serial interface, it's a packet interface > > + * using AT like commands. > > + */ > > So this shouldn't depend on TS 27.010 and instead be a generic gnss > serial driver. Hmm not sure if it makes sense to try to represent packet data as a virtual serial port :) But sure let's at least investigate it. > What does the interface look like over the corresponding USB port? > AT-commands without the U1234 prefix? I don't know if it's using the same commands as the ttyUSB* GNSS device seems disabled. From what I understand, gobi2000 has just $gps_start and $gps_stop commands for the ttyUSB* GNSS device. Those don't exist here. Also the command style seems to follow the modem firmware for various other devices on the modem. > No module parameters please. Either pick a good default or we need to > come up with a generic (sysfs) interface for polled drivers like this > one. OK yeah this could be a generic sysfs option. > How does your "aggressive pm" gsmmux implementation work with the gps if > there are no other clients keeping the modem awake? It seems the modem > would be suspended after 600 milliseconds after being woken up every 10 > seconds or so by the polling gnss driver? Well we still have /dev/gnss open, so GNSS stays active and won't get disabled until the device is closed. The shared GPIOs with the USB PHY are used to signal port traffic. > What happens to the satellite lock in between? Does the request block > until the gps has an updated position? It seems to regain the lock in about one or two seconds, so it's some kind of modem PM state for allowing the SoC to idle it seems. Regards, Tony
