From: Tony Lindgren <tony@atomide.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Dan Williams <dcbw@redhat.com>,
Sebastian Reichel <sre@kernel.org>,
Kishon Vijay Abraham I <kishon@ti.com>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
Mark Rutland <mark.rutland@arm.com>,
Marcel Partap <mpartap@gmx.net>,
Michael Scott <michael.scott@linaro.org>,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCHv4] phy: mapphone-mdm6600: Add USB PHY driver for MDM6600 on Droid 4
Date: Sun, 25 Mar 2018 17:22:59 -0700 [thread overview]
Message-ID: <20180326002259.GE5700@atomide.com> (raw)
In-Reply-To: <20180325225556.GA18141@amd>
* Pavel Machek <pavel@ucw.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
next prev parent reply other threads:[~2018-03-26 0:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-09 2:37 [PATCHv4] phy: mapphone-mdm6600: Add USB PHY driver for MDM6600 on Droid 4 Tony Lindgren
2018-03-09 9:44 ` Pavel Machek
2018-03-09 14:52 ` Tony Lindgren
2018-03-22 13:55 ` Pavel Machek
2018-03-22 16:46 ` Tony Lindgren
2018-03-22 19:28 ` Pavel Machek
2018-03-22 22:23 ` Dan Williams
2018-03-23 10:54 ` Pavel Machek
2018-03-23 11:35 ` Sebastian Reichel
2018-03-23 20:13 ` Pavel Machek
2018-03-24 13:59 ` Dan Williams
2018-03-24 14:25 ` Tony Lindgren
2018-03-24 20:02 ` Pavel Machek
2018-03-25 15:45 ` Tony Lindgren
2018-03-25 18:58 ` Pavel Machek
2018-03-25 20:52 ` Tony Lindgren
2018-03-25 22:55 ` Pavel Machek
2018-03-26 0:22 ` Tony Lindgren [this message]
2018-03-26 0:30 ` Tony Lindgren
2018-03-26 15:16 ` Dan Williams
2018-03-27 0:45 ` Tony Lindgren
2018-03-29 19:44 ` Pavel Machek
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=20180326002259.GE5700@atomide.com \
--to=tony@atomide.com \
--cc=dcbw@redhat.com \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=michael.scott@linaro.org \
--cc=mpartap@gmx.net \
--cc=pavel@ucw.cz \
--cc=robh+dt@kernel.org \
--cc=sre@kernel.org \
/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 NNTP newsgroup(s).