Received: by 10.213.65.68 with SMTP id h4csp2781908imn; Mon, 9 Apr 2018 08:57:43 -0700 (PDT) X-Google-Smtp-Source: AIpwx4/fW1R18eb0QFdOIC03yhna9DKaQg0313b4Slkk3CjnE0n8NG/p2Pj830oYoed68oqr4VlW X-Received: by 10.101.99.8 with SMTP id g8mr24901151pgv.182.1523289463349; Mon, 09 Apr 2018 08:57:43 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1523289463; cv=none; d=google.com; s=arc-20160816; b=P+r64ied9S8ZGacPfzAOBZRmpn2oLDZqoDRNB1ed7eEmW6q9P25A0oU1AWMa+x1xKB Ad9kBFNgzrKl1MxSU6A03QH0YRLBPp8oZ4xJA9QM111pAdeds/c/auAuemssPiGOsQhm lOTi2Inv/VjNo98GSiGTORIZcLvMuD4UZ9OUgGeLZQ7h8rsaHxmJd8HqbM5fsvaahyQr EjBbVPZ5JAYPBMyvVsQqRh39rWFt9xYCALi0hJKjCtNWpAmK35jLn0OkAnyGEBM0qM75 VQy3N/b+LBqC7JP/GJUVCFTWvxSLDRP+nmIR1qYdAD0EFv9v/lyoUfmb5IrEwABVzqL0 B4uQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:date:cc:to:from:subject:message-id :arc-authentication-results; bh=6Kp1kRTpA7GV1AXpiDx4L5GbsteT0lHRDq4uglz+zfA=; b=HiyZ/XQhN3UH0YDJc1t3jQe6FbXrGzIP5ZWQL3Xuow+HBnMrOeVa2ftleAQfK3uhMx 7ntUfFarZYPoiF9VxeG7qQqVqXOeKRuiiAb1M817thrD+0HRGdgxbd0B8TnUcWRPDFfm Pf+jhpc7fr0or046rBur1RitLHEaPmvQnixmflakkHGYFeJN38k8Wt9ZAcY91LcjXRYq VxkpQttR/ycEU/nCF+CkuPUf0uhy7MU9aeSeNaoswFg0XlJQH5E33mhaRr9TTJpLRnNF dIwjueL/y7BuArRzSfEidWVlPzgFzfuyRpR+U2gRzZG+VU/hHSjsQrEYcVOD4yi36yl8 HjJA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f14si393457pgn.597.2018.04.09.08.57.06; Mon, 09 Apr 2018 08:57:43 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753323AbeDIPxU (ORCPT + 99 others); Mon, 9 Apr 2018 11:53:20 -0400 Received: from mx3-rdu2.redhat.com ([66.187.233.73]:43684 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753209AbeDIPxS (ORCPT ); Mon, 9 Apr 2018 11:53:18 -0400 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.rdu2.redhat.com [10.11.54.4]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 768404023BAD; Mon, 9 Apr 2018 15:53:17 +0000 (UTC) Received: from ovpn-112-37.rdu2.redhat.com (ovpn-112-37.rdu2.redhat.com [10.10.112.37]) by smtp.corp.redhat.com (Postfix) with ESMTP id 362772026990; Mon, 9 Apr 2018 15:53:14 +0000 (UTC) Message-ID: Subject: Re: simultaneous voice/data works (was Re: call/normal switch was Re: omap4-droid4: voice call support was) From: Dan Williams To: Tony Lindgren Cc: Pavel Machek , Merlijn Wajer , Sebastian Reichel , Mark Brown , Liam Girdwood , Rob Herring , Lee Jones , Jaroslav Kysela , Takashi Iwai , alsa-devel@alsa-project.org, linux-omap@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, kernel@collabora.com Date: Mon, 09 Apr 2018 10:53:14 -0500 In-Reply-To: <20180409140847.GP5700@atomide.com> References: <67086fdd0cdd69142cb89cd00f90e5a580e6607a.camel@redhat.com> <20180402155754.GD5700@atomide.com> <20180403150444.GE5700@atomide.com> <20180403155023.GA14638@atrey.karlin.mff.cuni.cz> <20180403194419.GG5700@atomide.com> <20180406120423.GA18691@amd> <516eb3f7-e300-d59d-6a31-ab7545c656f1@wizzup.org> <20180407081000.GB7818@amd> <20180407122233.GA11302@amd> <20180409140847.GP5700@atomide.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.78 on 10.11.54.4 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.7]); Mon, 09 Apr 2018 15:53:17 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.7]); Mon, 09 Apr 2018 15:53:17 +0000 (UTC) for IP:'10.11.54.4' DOMAIN:'int-mx04.intmail.prod.int.rdu2.redhat.com' HELO:'smtp.corp.redhat.com' FROM:'dcbw@redhat.com' RCPT:'' Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2018-04-09 at 07:08 -0700, Tony Lindgren wrote: > * Dan Williams [180408 02:46]: > > On Sat, 2018-04-07 at 14:22 +0200, Pavel Machek wrote: > > > I tried --location-enable-gps-unmanaged , but that did not work > > > for > > > me. > > > > That requires a TTY that would spit out the GPS data; in this mode > > MM > > only sends the start/stop commands, and what comes out the GPS TTY > > is > > undefined (at least by MM). > > > > So unless you know that one of the 6600's TTYs does GPS and in what > > format it does GPS, then no. > > There should be a NMEA port within the unknown port range > ttyUSB[123]. > > Is there some easy way to enable --location-enable-gps-unmanaged for > testing so I can check if GPS gets enabled for one of the ports? Not all modems support all of the ModemManager location options; -unmanaged is only for devices that support sending the data to a separate port and for which we know the commands to do that. It looks like QMI has a way to direct the output to a specific device: // Enum to describe QMI PDS Output Devices enum eQMIPDSOutputDevices:UINT8 { eQMIPDSOutputDevices_NoneDisabled = 0, eQMIPDSOutputDevices_USB = 1, eQMIPDSOutputDevices_UART1 = 2, eQMIPDSOutputDevices_UART2 = 3, eQMIPDSOutputDevices_SharedMemory = 4, }; so we could add support for that to libqmi and then to ModemManager, which could help implement --location-enable-gps-unmanaged on alternate ports. But what might be simpler is implementing something like the "QMI GPS proxy" that already exists, but for ModemManager or libqmi directly. That way you can use QMI and get known formatting of the output data, but proxy it to a normal-looking NMEA tty? Instead of trying to figure out which TTY/UART/etc the information comes out of for each specific device and somehow encoding that into the platform. We know what the QMI ports are already, that's easy. We don't know what all the TTYs are for every given modem and hardcoding that info somewhere is error- prone and hard to keep up with. Dan