<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/usb/serial, branch v3.0.47</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers/usb/serial?h=v3.0.47</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers/usb/serial?h=v3.0.47'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2012-10-07T15:27:24Z</updated>
<entry>
<title>USB: qcaux: add Pantech vendor class match</title>
<updated>2012-10-07T15:27:24Z</updated>
<author>
<name>Bjørn Mork</name>
<email>bjorn@mork.no</email>
</author>
<published>2012-09-19T20:02:03Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=bd6a0fa2282e6cc0c951bda5e1e0e97291987e10'/>
<id>urn:sha1:bd6a0fa2282e6cc0c951bda5e1e0e97291987e10</id>
<content type='text'>
commit c638eb2872b3af079501e7ee44cbb8a5cce9b4b5 upstream.

The three Pantech devices UML190 (106c:3716), UML290 (106c:3718) and
P4200 (106c:3721) all use the same subclasses to identify vendor
specific functions.  Replace the existing device specific entries
with generic vendor matching, adding support for the P4200.

Signed-off-by: Bjørn Mork &lt;bjorn@mork.no&gt;
Cc: Thomas Schäfer &lt;tschaefer@t-online.de&gt;
Acked-by: Dan Williams &lt;dcbw@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>USB: ftdi_sio: add TIAO USB Multi-Protocol Adapter (TUMPA) support</title>
<updated>2012-10-07T15:27:24Z</updated>
<author>
<name>Antonio Ospite</name>
<email>ospite@studenti.unina.it</email>
</author>
<published>2012-09-23T07:57:25Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=3f72cbca902c6059a296f1df79b42020e75dbe4c'/>
<id>urn:sha1:3f72cbca902c6059a296f1df79b42020e75dbe4c</id>
<content type='text'>
commit 54575b05af36959dfb6a49a3e9ca0c2b456b7126 upstream.

TIAO/DIYGADGET USB Multi-Protocol Adapter (TUMPA) is an FTDI FT2232H
based device which provides an easily accessible JTAG, SPI, I2C, serial
breakout.

http://www.diygadget.com/tiao-usb-multi-protocol-adapter-jtag-spi-i2c-serial.html
http://www.tiaowiki.com/w/TIAO_USB_Multi_Protocol_Adapter_User%27s_Manual

FTDI FT2232H provides two serial channels (A and B), but on the TUMPA
channel A is dedicated to JTAG/SPI while channel B can be used for
UART/RS-232: use the ftdi_jtag_quirk to expose only channel B as
a usb-serial interface to userspace.

Signed-off-by: Antonio Ospite &lt;ospite@studenti.unina.it&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>USB: option: blacklist QMI interface on ZTE MF683</title>
<updated>2012-10-07T15:27:23Z</updated>
<author>
<name>Bjørn Mork</name>
<email>bjorn@mork.no</email>
</author>
<published>2012-09-19T20:02:12Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=952c5d808a20104a77d15ae857fd221182e27c10'/>
<id>urn:sha1:952c5d808a20104a77d15ae857fd221182e27c10</id>
<content type='text'>
commit 160c9425ac52cb30502be2d9c5e848cec91bb115 upstream.

Interface #5 on ZTE MF683 is a QMI/wwan interface.

Signed-off-by: Bjørn Mork &lt;bjorn@mork.no&gt;
Cc: Shawn J. Goff &lt;shawn7400@gmail.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>USB: ftdi-sio: add support for more Physik Instrumente devices</title>
<updated>2012-10-02T16:47:38Z</updated>
<author>
<name>Éric Piel</name>
<email>piel@delmic.com</email>
</author>
<published>2012-09-04T15:25:06Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=15e87566fc6fafda50aca428dc068f9c157ec68f'/>
<id>urn:sha1:15e87566fc6fafda50aca428dc068f9c157ec68f</id>
<content type='text'>
commit dafc4f7be1a556ca3868d343c00127728b397068 upstream.

Commit b69cc672052540 added support for the E-861.  After acquiring a C-867, I
realised that every Physik Instrumente's device has a different PID. They are
listed in the Windows device driver's .inf file. So here are all PIDs for the
current (and probably future) USB devices from Physik Instrumente.

Compiled, but only actually tested on the E-861 and C-867.

Signed-off-by: Éric Piel &lt;piel@delmic.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>USB: ftdi_sio: do not claim CDC ACM function</title>
<updated>2012-10-02T16:47:38Z</updated>
<author>
<name>Bjørn Mork</name>
<email>bjorn@mork.no</email>
</author>
<published>2012-09-10T10:01:05Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=0c361a311e59d5ce7ee86b022b0dc1114e79bdbd'/>
<id>urn:sha1:0c361a311e59d5ce7ee86b022b0dc1114e79bdbd</id>
<content type='text'>
commit f08dea734844aa42ec57c229b0b73b3d7d21f810 upstream.

The Microchip vid:pid 04d8:000a is used for their CDC ACM
demo firmware application.  This is a device with a single
function conforming to the CDC ACM specification and with
the intention of demonstrating CDC ACM class firmware and
driver interaction.  The demo is used on a number of
development boards, and may also be used unmodified by
vendors using Microchip hardware.

Some vendors have re-used this vid:pid for other types of
firmware, emulating FTDI chips. Attempting to continue to
support such devices without breaking class based
applications that by matching on interface
class/subclass/proto being ff/ff/00.  I have no information
about the actual device or interface descriptors, but this
will at least make the proper CDC ACM devices work again.
Anyone having details of the offending device's descriptors
should update this entry with the details.

Reported-by: Florian Wöhrl &lt;fw@woehrl.biz&gt;
Reported-by: Xiaofan Chen &lt;xiaofanc@gmail.com&gt;
Cc: Alan Cox &lt;alan@linux.intel.com&gt;
Cc: Bruno Thomsen &lt;bruno.thomsen@gmail.com&gt;
Signed-off-by: Bjørn Mork &lt;bjorn@mork.no&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>USB: ftdi_sio: PID for NZR SEM 16+ USB</title>
<updated>2012-10-02T16:47:38Z</updated>
<author>
<name>Horst Schirmeier</name>
<email>horst@schirmeier.com</email>
</author>
<published>2012-08-30T22:00:28Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=a16bd7c72f5579461fd2c6059f2bf75ad6355ec8'/>
<id>urn:sha1:a16bd7c72f5579461fd2c6059f2bf75ad6355ec8</id>
<content type='text'>
commit 26a538b9ea2a3ee10dafc0068f0560dfd7b7ba37 upstream.

This adds the USB PID for the NZR SEM 16+ USB energy monitor device
&lt;http://www.nzr.de&gt;.  It works perfectly with the GPL software on
&lt;http://schou.dk/linux/sparometer/&gt;.

Signed-off-by: Horst Schirmeier &lt;horst@schirmeier.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>USB: option: replace ZTE K5006-Z entry with vendor class rule</title>
<updated>2012-10-02T16:47:24Z</updated>
<author>
<name>Bjørn Mork</name>
<email>bjorn@mork.no</email>
</author>
<published>2012-09-11T07:40:31Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=d982d2f4e90cc354b5428d8d951784e0a3007bf3'/>
<id>urn:sha1:d982d2f4e90cc354b5428d8d951784e0a3007bf3</id>
<content type='text'>
commit ba9edaa468869a8cea242a411066b0f490751798 upstream.

Fix the ZTE K5006-Z entry so that it actually matches anything

  commit f1b5c997 USB: option: add ZTE K5006-Z

added a device specific entry assuming that the device would use
class/subclass/proto == ff/ff/ff like other ZTE devices. It
turns out that ZTE has started using vendor specific subclass
and protocol codes:

T:  Bus=01 Lev=01 Prnt=01 Port=03 Cnt=01 Dev#=  4 Spd=480  MxCh= 0
D:  Ver= 2.00 Cls=00(&gt;ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=19d2 ProdID=1018 Rev= 0.00
S:  Manufacturer=ZTE,Incorporated
S:  Product=ZTE LTE Technologies MSM
S:  SerialNumber=MF821Vxxxxxxx
C:* #Ifs= 5 Cfg#= 1 Atr=c0 MxPwr=500mA
I:* If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=86 Prot=10 Driver=(none)
E:  Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms
I:* If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=02 Prot=05 Driver=(none)
E:  Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms
I:* If#= 2 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=02 Prot=01 Driver=(none)
E:  Ad=83(I) Atr=03(Int.) MxPS=  64 Ivl=2ms
E:  Ad=84(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=03(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms
I:* If#= 3 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=06 Prot=00 Driver=qmi_wwan
E:  Ad=85(I) Atr=03(Int.) MxPS=  64 Ivl=2ms
E:  Ad=86(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=04(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms
I:* If#= 4 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
E:  Ad=05(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=87(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms

We do not have any information on how ZTE intend to use these
codes, but let us assume for now that the 3 sets matching
serial functions in the K5006-Z always will identify a serial
function in a ZTE device.

Cc: Thomas Schäfer &lt;tschaefer@t-online.de&gt;
Signed-off-by: Bjørn Mork &lt;bjorn@mork.no&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>usb: serial: mos7840: Fixup mos7840_chars_in_buffer()</title>
<updated>2012-08-26T22:12:13Z</updated>
<author>
<name>Mark Ferrell</name>
<email>mferrell@uplogix.com</email>
</author>
<published>2012-07-24T19:15:13Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=edbc37fd3930900161aca75dd3684825179ca091'/>
<id>urn:sha1:edbc37fd3930900161aca75dd3684825179ca091</id>
<content type='text'>
commit 5c263b92f828af6a8cf54041db45ceae5af8f2ab upstream.

 * Use the buffer content length as opposed to the total buffer size.  This can
   be a real problem when using the mos7840 as a usb serial-console as all
   kernel output is truncated during boot.

Signed-off-by: Mark Ferrell &lt;mferrell@uplogix.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>USB: ftdi_sio: Add VID/PID for Kondo Serial USB</title>
<updated>2012-08-26T22:12:12Z</updated>
<author>
<name>Ozan Çağlayan</name>
<email>ozancag@gmail.com</email>
</author>
<published>2012-08-10T14:25:10Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=d0f56add7cd65221d04964de9cc78bddebe2ecae'/>
<id>urn:sha1:d0f56add7cd65221d04964de9cc78bddebe2ecae</id>
<content type='text'>
commit 7724a1edbe463b06d4e7831a41149ba095b16c53 upstream.

This adds VID/PID for Kondo Kagaku Co. Ltd. Serial USB Adapter
interface:
http://www.kondo-robot.com/EN/wp/?cat=28

Tested by controlling an RCB3 board using libRCB3.

Signed-off-by: Ozan Çağlayan &lt;ozancag@gmail.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>USB: option: add ZTE K5006-Z</title>
<updated>2012-08-26T22:12:12Z</updated>
<author>
<name>Bjørn Mork</name>
<email>bjorn@mork.no</email>
</author>
<published>2012-08-15T13:43:33Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=bb82df1a3fd0ab9ddab5134abe3e79917cd90954'/>
<id>urn:sha1:bb82df1a3fd0ab9ddab5134abe3e79917cd90954</id>
<content type='text'>
commit f1b5c997e68533df1f96dcd3068a231bca495603 upstream.

The ZTE (Vodafone) K5006-Z use the following
interface layout:

00 DIAG
01 secondary
02 modem
03 networkcard
04 storage

Ignoring interface #3 which is handled by the qmi_wwan
driver.

Signed-off-by: Bjørn Mork &lt;bjorn@mork.no&gt;
Cc: Thomas Schäfer &lt;tschaefer@t-online.de&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
</feed>
