lkml.org 
[lkml]   [2018]   [Mar]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: omap4-droid4: voice call support was Re: [PATCHv5,5/5] ARM: dts: omap4-droid4: add soundcard
Hi,

On Thu, Mar 29, 2018 at 06:59:04AM -0700, Tony Lindgren wrote:
> > I think cpcap is always the clock and frame master, but I think
> > mdm6600 is the remote side and OMAP is not involved at all.
>
> OK. So could it be just an alsamixer on/off toggle then for
> "Modem" or something similar?

I think so. We might want to have an "Mode" enum instead, though.
That can be extended, once we unlock the other modes (bluetooth,
bluetooth call).

> > > 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
>
> There's a typo above, it should be just ATD123 where 123 is the
> number.
>
> I was just doing few test calls to robots. Payback time for all
> the robocalls, you know! :)
>
> > > And I do hear a voice talking over the speakerphone :) Sorry have not tested the
> > > mic yet..
>
> And calling a person I can hear the other end but the mic is
> not working. So maybe I need to tweak the alsamixer settings
> too for mic?

Your override kills most settings from alsamixer. You can try to
just override CPCAP_REG_VAUDIOC, CPCAP_REG_CC and CPCAP_REG_CDI
and setup everything else with alsamixer.

-- Sebastian
[unhandled content-type:application/pgp-signature]
\
 
 \ /
  Last update: 2018-03-29 17:46    [W:0.143 / U:0.480 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site