Messages in this thread | | | Date | Fri, 30 Mar 2018 12:57:42 +0200 | From | Sebastian Reichel <> | Subject | Re: omap4-droid4: voice call support was Re: [PATCHv5,5/5] ARM: dts: omap4-droid4: add soundcard |
| |
Hi,
On Thu, Mar 29, 2018 at 09:06:11AM -0700, Tony Lindgren wrote: > * Sebastian Reichel <sebastian.reichel@collabora.co.uk> [180329 15:47]: > > 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). > > OK. Seems in addition to the "Mode" enum, we also need > some other switch for modem on and off toggle?
I don't think so. DAPM should automatically power on/off the modem if there is a valid path from some CPCAP output/input. Since the mode enum will "disconnect" the modem in the DAPM graph, it should be enabled/disabled automatically.
> I guess most people want to save the preferred "Mode" enum, > then for the duration of the call enable the selected mode. > > And I guess the mute is already there for the mic with 'm' > in alsamixer for conf calls :)
Yes.
-- Sebastian [unhandled content-type:application/pgp-signature] | |