Received: by 2002:ac0:8845:0:0:0:0:0 with SMTP id g63csp1900894img; Wed, 27 Feb 2019 07:20:02 -0800 (PST) X-Google-Smtp-Source: AHgI3IYe73oxToHw16kN/25eB6yqHdyCxSVOmp4p0NcDMIQsm0qm15x1o5ceczroTmuHHvxG81/3 X-Received: by 2002:a62:5c4:: with SMTP id 187mr2135841pff.153.1551280802431; Wed, 27 Feb 2019 07:20:02 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1551280802; cv=none; d=google.com; s=arc-20160816; b=kHNlib2TsL8TnoHbEYDCZHLV6GALUTwF4j3MPZEM84//HM7PEkijh/mdiucWPn5AKz wOuTh2jG03r2WxQCbfpbQxF37lb7ATSCkmdGLp36iuNJ62SoIBeNZ6+xeV3hlv9lOax4 9TYDpIHPh3wU2Wr4ZeMRXs3K97O1OYYTRV9DWariccNH01PveP5LTapLcbhmgo3IrNk0 X0YpcQPVY2qMCABhywOPrprLTOszOzU09SiXyriRTNnHd4+8IzRvR+GPCosv0PZdVi5g 4sBkRA9nkV3hC7tH6XQmJGbZjh/ion/UEfZ6OdPLsGhy7QiaCc0WV+/KNA+vL35EUL0X rOvw== 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 :user-agent:message-id:in-reply-to:date:references:subject:cc:to :from; bh=+bpC6Qdy679GsqAHZwiZi9kUcQ+CaVmgxQRrpI31jeg=; b=lnwiRe5NYCLueJQinqImqm+FShCTrA4cR7RNST9Dx22jV3R+YHTAvuru9CR5eE1J+h RRR+P2y34M4G1fUiEiNl9ctx+sWQ2u3n3RCoCthHc6MjZcPtpR8nSQ212Ey4zV5QxeeS LqqHi2prxCYzALuo2JpNA0W3Hg6SsVFydhnFdd0ut/dRMAx9jpybbNfqOk6nMdYxTUsw p2bJoZC0jYRWJbGdwG3MSpTi6c2hF71dY/w19ykxd4dJc2gbxGFtzgIcYQlPV86QR+rd hx7th9n7iXE0vxPDP+sEmj2EE+SCoKlcvrObFNVLREKoV4qglt4ddtFhPOmbfAKPNeUe 5W4w== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id u6si15217918pga.430.2019.02.27.07.19.44; Wed, 27 Feb 2019 07:20:02 -0800 (PST) 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730372AbfB0OdB convert rfc822-to-8bit (ORCPT + 99 others); Wed, 27 Feb 2019 09:33:01 -0500 Received: from unicorn.mansr.com ([81.2.72.234]:39750 "EHLO unicorn.mansr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730224AbfB0OdB (ORCPT ); Wed, 27 Feb 2019 09:33:01 -0500 Received: by unicorn.mansr.com (Postfix, from userid 51770) id D630615632; Wed, 27 Feb 2019 14:32:58 +0000 (GMT) From: =?iso-8859-1?Q?M=E5ns_Rullg=E5rd?= To: Johan Hovold Cc: =?iso-8859-1?Q?Bj=F8rn?= Mork , Greg Kroah-Hartman , linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] USB: serial: option: set driver_info for SIM5218 and compatibles References: <20190226170710.12709-1-mans@mansr.com> <20190227083342.GJ4747@localhost> <20190227131315.GO4747@localhost> Date: Wed, 27 Feb 2019 14:32:58 +0000 In-Reply-To: <20190227131315.GO4747@localhost> (Johan Hovold's message of "Wed, 27 Feb 2019 14:13:15 +0100") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Johan Hovold writes: > Adding Bj?rn. > > On Wed, Feb 27, 2019 at 11:57:16AM +0000, M?ns Rullg?rd wrote: >> Johan Hovold writes: >> >> > On Tue, Feb 26, 2019 at 05:07:10PM +0000, Mans Rullgard wrote: >> >> The SIMCom SIM5218 and compatible devices have 5 USB interfaces, only 4 >> >> of which are serial ports. The fifth is a network interface supported >> >> by the qmi-wwan driver. Furthermore, the serial ports do not support >> >> modem control signals. Add driver_info flags to reflect this. >> >> >> >> Signed-off-by: Mans Rullgard >> >> --- >> >> drivers/usb/serial/option.c | 3 ++- >> >> 1 file changed, 2 insertions(+), 1 deletion(-) >> >> >> >> diff --git a/drivers/usb/serial/option.c b/drivers/usb/serial/option.c >> >> index fb544340888b..af4cbfecc3ff 100644 >> >> --- a/drivers/usb/serial/option.c >> >> +++ b/drivers/usb/serial/option.c >> >> @@ -1066,7 +1066,8 @@ static const struct usb_device_id option_ids[] = { >> >> .driver_info = RSVD(3) }, >> >> { USB_DEVICE(QUALCOMM_VENDOR_ID, 0x6613)}, /* Onda H600/ZTE MF330 */ >> >> { USB_DEVICE(QUALCOMM_VENDOR_ID, 0x0023)}, /* ONYX 3G device */ >> >> - { USB_DEVICE(QUALCOMM_VENDOR_ID, 0x9000)}, /* SIMCom SIM5218 */ >> >> + { USB_DEVICE(QUALCOMM_VENDOR_ID, 0x9000), /* SIMCom SIM5218 */ >> >> + .driver_info = NCTRL(0) | NCTRL(1) | NCTRL(2) | NCTRL(3) | RSVD(4) }, >> >> /* Quectel products using Qualcomm vendor ID */ >> >> { USB_DEVICE(QUALCOMM_VENDOR_ID, QUECTEL_PRODUCT_UC15)}, >> >> { USB_DEVICE(QUALCOMM_VENDOR_ID, QUECTEL_PRODUCT_UC20), >> > >> > Could you please provide the output of usb-devices (or lsusb -v) for >> > this device? >> >> lsusb -v: >> [...] > So the patch looks fine to me. The fifth interface is QMI, but hasn't > been available for use until now then, and this seems to have been the > vendors idea from the start: > > http://www.microchip.ua/simcom/WCDMA/APPNOTES/SIMCom_3G_Linux_driver_Application%20Note_V1.00.pdf That document predates the qmi-wwan driver in the kernel. Note that this driver has an ID table entry for interface 4 of this device. Right now, whichever driver is probed first claims that interface. I haven't actually tried using the QMI interface, though. > And you're seeing errors when opening ports 0-3 due to the DTR calls > which I guess no one noticed or cared about before? Right, some userspace tools complain about this. > Before you sent me the lsusb I searched for it and came across the below > thread where Bj?rn's having a go at SIMCom. In it there's output from a > second device using the same id but with entirely different descriptors. > > https://forum.openwrt.org/t/lte-wireless-module-support-by-openwrt-led-on-tplink/13586?page=3 > > If this is a common theme with this vendor we may need to be extra > careful when making changes. Isn't this a common theme with most USB vendors, especially wireless things? Regardless, setting the NCTRL flag should be harmless. -- M?ns Rullg?rd