[PATCH] USB: serial: simple: add Motorola Tetra driver for TPG2200

2019-01-06 Thread Max Schulze
uct=TETRA PEI interface C: #Ifs= 2 Cfg#= 1 Atr=80 MxPwr=500mA I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=usb_serial_simple I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=usb_serial_simple Signed-off-by: Max Schulze Tested-by: Max Schulze --- drivers/usb/serial/

Re: [PATCH v3] USB: serial: option: add id for Motorola Solutions TETRA PEI

2018-01-15 Thread Max Schulze
=00 Prot=00 Driver=(none) > > Note that these devices do not support the CDC SET_CONTROL_LINE_STATE > request (for any interface). > > Reported-by: Max Schulze > Cc: stable > Signed-off-by: Johan Hovold > --- > drivers/usb/serial/Kconfig | 1 + > dri

[PATCH v3] USB: serial: option: add id for Motorola Solutions TETRA PEI

2018-01-12 Thread Max Schulze
=ff(vend.) Sub=00 Prot=00 Driver=(none) I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none) Signed-off-by: Max Schulze --- v3: reformatted Patch drivers/usb/serial/option.c | 6 ++ 1 file changed, 6 insertions(+) diff --git a/drivers/usb/serial/option.c b/drivers/usb/ser

[PATCH v2] USB: serial: option: add id for Motorola Solutions TETRA PEI

2018-01-12 Thread Max Schulze
Add Motorola Device ID and blacklist entry to the driver usb/serial/option Signed-off-by: Max Schulze --- v2: reformatted Patch, first version was declined by GK-H's Bot Thanks for the help, Johan! To an URB setup request from the host bmRequestType: 0x21 bRequest: 34 wValue: 0x0003 wInd

Re: Help needed debugging Motorola Solutions TETRA PEI interface

2018-01-08 Thread Max Schulze
Thanks Johan for taking a look. Am 08.01.2018 um 17:30 schrieb Johan Hovold: > Adding the device ids and a quirk to cdc_acm.c >>> .driver_info = NO_UNION_NORMAL, >> does only suppress the "Zero length" message. > Do you then get a ttyACMn device? Or some other error? Nothing more. No ttyACM devic

Help needed debugging Motorola Solutions TETRA PEI interface

2018-01-04 Thread Max Schulze
Hello, I need some advice how to debug a device, that under Windows presents 2 virtual com ports. Windows .sys. file mentions a "Jungo CDC ACM OBEX Driver". I get the following dmesg output > [ 1700.263981] usb 1-1.4: new full-speed USB device number 10 using > ehci-pci > [ 1700.378186] usb 1-1

[PATCH] USB: serial: ftdi_sio: add id for Airbus DS P8GR

2017-12-20 Thread Max Schulze
Add AIRBUS_DS_P8GR device IDs to ftdi_sio driver. Signed-off-by: Max Schulze --- The device allows a simple AT style modem command set. Tested up to the advertised maximum of 115200 baud. Bus 001 Device 013: ID 1e8e:6001 Device Descriptor: bLength18 bDescriptorType