From: Tony Lindgren <tony@atomide.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Rob Herring <robh@kernel.org>, Marcel Partap <mpartap@gmx.net>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
omerlle@gmail.com, Merlijn Wajer <merlijn@wizzup.org>,
linux-kernel@vger.kernel.org, Johan Hovold <johan@kernel.org>,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
NeKit <nekit1000@gmail.com>,
linux-arm-kernel@lists.infradead.org,
Michael Scott <hashcode0f@gmail.com>,
Sebastian Reichel <sre@kernel.org>,
linux-omap@vger.kernel.org,
Jarkko Nikula <jarkko.nikula@bitmer.com>
Subject: Re: WIP Droid 4 voice calls, GNSS & PM with a TS 27.010 serdev driver
Date: Wed, 16 Jan 2019 07:09:56 -0800 [thread overview]
Message-ID: <20190116150956.GN5544@atomide.com> (raw)
In-Reply-To: <20190116145904.GM5544@atomide.com>
* Tony Lindgren <tony@atomide.com> [190116 14:59]:
> * Pavel Machek <pavel@ucw.cz> [190116 13:58]:
> > And I wanted to ask -- did you figure out how to acknowledge the
> > SMSs? +CGNNA does not seem to do the job:
> >
> > 07912470338016...
> > AT+CGNMA=1
> > +CGNMA:ERROR=9
>
> Yeah the scripts in droid4-sms-tools git repo work for me for sending
> and receiving. They do not work with cdma currently as the format is
> different.
>
> Maybe you've managed to change the mode of the modem to queue the
> messages with the at commands to the usb port?
>
> You are reading and writing to /dev/motmdm9 for incoming sms right?
To debug, you can modprobe n_gsm debug=0xff and you'll see all the
packet data in dmesg, maybe email me the dmesg output of your ack
command packet data?
Or compare against what Android is doing, you can echo 0x7fffffff to
the ts27010 sysfs debug file somewhere to see similar packet data
with logcat -b radio.
Regards,
Tony
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-01-16 15:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 0:44 WIP Droid 4 voice calls, GNSS & PM with a TS 27.010 serdev driver Tony Lindgren
2018-12-18 12:46 ` Pavel Machek
2018-12-18 15:36 ` Tony Lindgren
2018-12-18 20:22 ` Pavel Machek
2018-12-18 21:53 ` Tony Lindgren
2019-01-16 13:48 ` Pavel Machek
2019-01-17 2:54 ` Tony Lindgren
2019-01-17 12:51 ` Pavel Machek
2018-12-22 23:05 ` Pavel Machek
2018-12-23 10:33 ` Pavel Machek
2018-12-23 11:10 ` Pavel Machek
2018-12-23 15:51 ` Tony Lindgren
2018-12-23 19:59 ` Pavel Machek
2018-12-26 21:16 ` Pavel Machek
2018-12-27 10:16 ` Pavel Machek
2018-12-28 19:31 ` Tony Lindgren
2018-12-28 20:46 ` Pavel Machek
2018-12-28 22:28 ` Tony Lindgren
2018-12-28 23:25 ` Pavel Machek
2018-12-28 23:34 ` Tony Lindgren
2018-12-31 22:20 ` Tony Lindgren
2019-01-16 13:58 ` Pavel Machek
2019-01-16 14:59 ` Tony Lindgren
2019-01-16 15:09 ` Tony Lindgren [this message]
2019-01-16 23:06 ` 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=20190116150956.GN5544@atomide.com \
--to=tony@atomide.com \
--cc=hashcode0f@gmail.com \
--cc=jarkko.nikula@bitmer.com \
--cc=johan@kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=merlijn@wizzup.org \
--cc=mpartap@gmx.net \
--cc=nekit1000@gmail.com \
--cc=omerlle@gmail.com \
--cc=pavel@ucw.cz \
--cc=peter.ujfalusi@ti.com \
--cc=robh@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).