[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180326002259.GE5700@atomide.com>
Date: Sun, 25 Mar 2018 17:22:59 -0700
From: Tony Lindgren <tony@...mide.com>
To: Pavel Machek <pavel@....cz>
Cc: Dan Williams <dcbw@...hat.com>, Sebastian Reichel <sre@...nel.org>,
Kishon Vijay Abraham I <kishon@...com>,
linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org,
linux-omap@...r.kernel.org, devicetree@...r.kernel.org,
Mark Rutland <mark.rutland@....com>,
Marcel Partap <mpartap@....net>,
Michael Scott <michael.scott@...aro.org>,
Rob Herring <robh+dt@...nel.org>
Subject: Re: [PATCHv4] phy: mapphone-mdm6600: Add USB PHY driver for MDM6600
on Droid 4
* Pavel Machek <pavel@....cz> [180325 22:57]:
> Hi!
>
> > > > > Hmm. Interesting. Anyway, for me ttyUSB4 is interesting, as it seems
> > > > > to react to AT commands, and in particular reacts to ADT123; (; is
> > > > > important).
> > > >
> > > > Is that to dial a voice call?
> > >
> > > Yes. And it is ATD123; not ATD.
> >
> > Strange, no semicolon is needed when using /dev/gsmtty to
> > dial a voice call with my current pile of pending changes,
> > just doing ATD123 dials..
>
> Interesting. Maybe I made some mistake in experiment.
Looks like on /dev/ttyUSB4 doing AT+COPS? or AT+CREG? won't work
while on /dev/gsmtty1 they work. So /dev/ttyUSB4 seems to a subset of
what's available over n_gsm on ch1. Anyways, good to hear that
/dev/ttyUSB4 can be used to debug voice calls :)
> Thanks for hints, it would not be bad to get gps working. But .. voice
> calls. Those are important :-).
Yup, please keep us posted :) Meanwhile, I'll slowly continue
getting the n_gsm stuff working.
Tony
Powered by blists - more mailing lists