Re: omap4-droid4: voice call support was Re: [PATCHv5, 5/5] ARM: dts: omap4-droid4: add soundcard

Michael Nazzareno Trimarchi
2018-03-30T15:25:24Z

Hi

On Fri., 30 Mar. 2018, 11:22 pm Tony Lindgren, <tony@atomide.com> wrote:

> * Merlijn Wajer <merlijn@wizzup.org> [180330 13:09]:
> > On 30/03/18 12:37, Pavel Machek wrote:
> > > On Thu 2018-03-29 14:56:13, Tony Lindgren wrote:
> > >> * Pavel Machek <pavel@ucw.cz> [180329 18:41]:
> > >>> Thanks. I got call working including outgoing audio: in capture
> > >>> settings, right->mic 1, Mic1 + Mic2 in alsamixer -> 100%. But I had
> > >>> the other phone muted, so I don't yet know if such call would be of
> > >>> usable quality.
> > >>
> > >> Great, good to hear that :)
> > >
> > > I also got ofonod to work, with rather crazy hacks. But I now have
> > > incoming/outgoing calls with GUI :-).
> >
> > Would you mind sharing those hacks - I would like to play around with
> > ofonod as well. Maybe I can help with a way forward.
>
> Yeah that would be fun to play with :)
>
> Below is a patch that works better at least for ModemManager,
> does anybody have ideas what the unused three ports might be?
>
> I wonder if ofono can use /dev/ttyUSB0 CQDM port?
>

One of them can be used proprably to bridge debug for modem certification.
This is usually disable for production device. The other could used for
unsolicited response of GPS function if exists in this modem

Michael

>
> Regards,
>
> Tony
>
> 8< -------------------------
> From tony Mon Sep 17 00:00:00 2001
> From: Tony Lindgren <tony@atomide.com>
> Date: Sun, 19 Nov 2017 19:55:56 -0800
> Subject: [PATCH] USB: qcaux: Add droid 4 mdm6600 modem
>
> We have five USB ports on mdm6600 modem and does not have the same
> layout as layout as Gobi 1K/2K/etc devices listed in qcserial.c
>
> So we should not be adding them to qcserial.c but instead use
> qcaux.c or option.c as noted by Dan Williams <dcbw@redhat.com>.
>
> The ttyUSB ports detected by ModemManager are:
>
> ttyUSB0 CQDM-capable
> ttyUSB1 no response
> ttyUSB2 no response
> ttyUSB3 no response
> ttyUSB4 AT-capable
>
> Note that it takes a while for ModemManager to start while it's
> detecting the ports, so we may want to eventually limit the ports.
>
> So far no luck finding out what the unused three ports are, maybe
> there is NMEA there if somebody knows how to enable it.
>
> Signed-off-by: Tony Lingren <tony@atomide.com>
> ---
> drivers/usb/serial/qcaux.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/usb/serial/qcaux.c b/drivers/usb/serial/qcaux.c
> --- a/drivers/usb/serial/qcaux.c
> +++ b/drivers/usb/serial/qcaux.c
> @@ -66,6 +66,7 @@ static const struct usb_device_id id_table[] = {
> { USB_VENDOR_AND_INTERFACE_INFO(UTSTARCOM_VENDOR_ID, 0xff, 0xfe,
> 0xff) }, /* WMC */
> { USB_VENDOR_AND_INTERFACE_INFO(UTSTARCOM_VENDOR_ID, 0xff, 0xff,
> 0xff) }, /* DIAG */
> { USB_DEVICE_AND_INTERFACE_INFO(0x1fac, 0x0151, 0xff, 0xff, 0xff)
> },
> + { USB_DEVICE_AND_INTERFACE_INFO(0x22b8, 0x2a70, 0xff, 0xff, 0xff)
> },
> { },
> };
> MODULE_DEVICE_TABLE(usb, id_table);
> --
> 2.16.3
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>