[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5942081F7727964D830FC876E62CA856014CC36A3F@MHQMBX02.moxa.com>
Date: Fri, 27 Apr 2018 02:14:55 +0000
From: SZ Lin (林上智) <SZ.Lin@...a.com>
To: Dan Williams <dcbw@...hat.com>, Johan Hovold <johan@...nel.org>,
"Lars Melin" <larsm17@...il.com>
CC: Bjørn Mork <bjorn@...k.no>,
stable <stable@...r.kernel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] USB: serial: option: adding support for ublox R410M
<snip>
>
> Option is likely the right driver for this device.
>
> qcaux was mainly for mobile phones that have a TTY (often cdc-acm) as the modem port
> and a secondary DIAG/DM port driven by qcaux. The DM port doesn't have an interrupt
> endpoint thus it's not a normal modem port requiring the larger buffers of option and its
> control signaling.
>
> qcserial (as Bjorn mentioned) is only for actual Gobi-type devices with the specific layouts
> and the firmware loading requirement where the 1K and 2K devices start in a special
> 1-port mode waiting for firmware and then become 4-port devices on firmware reboot.
>
> Dan
Thank you all. I believe that many people are confused in selecting serial driver (option and qcserial)
for QUALCOMM based module. This thread has provided clearly and properly presented the different
between them.
SZ
Powered by blists - more mailing lists