[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180329163450.GQ5700@atomide.com>
Date: Thu, 29 Mar 2018 09:34:50 -0700
From: Tony Lindgren <tony@...mide.com>
To: Pavel Machek <pavel@....cz>
Cc: Sebastian Reichel <sebastian.reichel@...labora.co.uk>,
Mark Brown <broonie@...nel.org>,
Liam Girdwood <lgirdwood@...il.com>,
Rob Herring <robh+dt@...nel.org>,
Lee Jones <lee.jones@...aro.org>,
Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.com>, alsa-devel@...a-project.org,
linux-omap@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, kernel@...labora.com,
Dan Williams <dcbw@...hat.com>
Subject: Re: omap4-droid4: voice call support was Re: [PATCHv5,5/5] ARM: dts:
omap4-droid4: add soundcard
* Pavel Machek <pavel@....cz> [180329 16:09]:
> > Then using the n_gsm ts 27.010 uart mux, I dial:
> >
> > ./ngsm-rw 1 "AT+CFUN=1" # connect to network
> > U0001+CFUN:OK
> > ./ngsm-rw 2 "AT+CMUT=0" # unmute speaker over ch2, do this over qmi?
> > U0001+CMUT:OK
> > ./ngsm-rw 1 "ATD#123" # dial number
> > U0001D:OK
> >
> > And I do hear a voice talking over the speakerphone :) Sorry have not tested the
> > mic yet..
>
> Hehe, ok, that's fun! I don't need +CMUT=0. It gave me error but then
> the call worked, anyway... (I'm working with ttyUSB4).
Oh interesting. So maybe Android is doing AT+CMUT=0 for some other
modems and it's not really needed? Or you have settings preserved
from warm boot from Android?
I did not have any luck with ttyUSB4 last night. Did you dial with
ATD123; or ATD123? So is the semicolon really needed?
> I don't know how to hang the call up. ATH did not work for me.
OK ATH works for me on n_gsm channel 1.
> And no, microphone does not work.
Yeah so conf calls only for now.
Tony
Powered by blists - more mailing lists