All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Max Schulze <max.schulze@posteo.de>
Cc: Johan Hovold <johan@kernel.org>,
	gregkh@linuxfoundation.org, linux-usb@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [v3] USB: serial: option: add id for Motorola Solutions TETRA PEI
Date: Thu, 18 Jan 2018 14:26:07 +1100	[thread overview]
Message-ID: <20180118032607.GF3286@localhost> (raw)

On Tue, Jan 16, 2018 at 12:12:33AM +0100, Max Schulze wrote:
> 
> > This indicates that option isn't the right driver for this for device.
> >
> > I think we should add a new simple driver for it instead, which reports
> > that modem control isn't (yet) supported (yes, your python script would
> > need to be updated). This can be extended into a "real" driver, should
> > we learn more about the protocol used.
> 
> Thank you. Tested with miniterm.py - it doesn't need any changes because
> no erroneous URB's are sent.

That's good. In your initial mail you mentioned that it was doing a
TIOCMBIS that was failing with the generic driver (which is essentially
the same thing as a "simple" driver).

> [  172.249297] usb_serial_simple 1-1.4:1.0: motorola_tetra converter
> detected
> [  172.249403] usb 1-1.4: motorola_tetra converter now attached to ttyUSB0
> [  172.249502] usb_serial_simple 1-1.4:1.1: motorola_tetra converter
> detected
> [  172.249578] usb 1-1.4: motorola_tetra converter now attached to ttyUSB1
> 
> > >From a7ab87acf85b67303e7bf606734176a365aae9cd Mon Sep 17 00:00:00 2001
> > From: Johan Hovold <johan@kernel.org>
> > Date: Fri, 12 Jan 2018 17:53:35 +0100
> > Subject: [PATCH] USB: serial: simple: add Motorola Tetra driver
> >
> > Add new Motorola Tetra (simple) driver for Motorola Solutions TETRA PEI
> > devices.
> >
> > D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
> > P:  Vendor=0cad ProdID=9011 Rev=24.16
> > S:  Manufacturer=Motorola Solutions Inc.
> > S:  Product=Motorola Solutions 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=(none)
> > I:  If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=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 <max.schulze@posteo.de>
> > Cc: stable <stable@vger.kernel.org>
> > Signed-off-by: Johan Hovold <johan@kernel.org>

> Works as-is. Tested in miniterm.py and minicom.
> 
> Tested-by: Max Schulze <max.schulze@posteo.de>

Thanks for testing!

Johan
---
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Johan Hovold <johan@kernel.org>
To: Max Schulze <max.schulze@posteo.de>
Cc: Johan Hovold <johan@kernel.org>,
	gregkh@linuxfoundation.org, linux-usb@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] USB: serial: option: add id for Motorola Solutions TETRA PEI
Date: Thu, 18 Jan 2018 14:26:07 +1100	[thread overview]
Message-ID: <20180118032607.GF3286@localhost> (raw)
In-Reply-To: <1405adb5-8e74-b02a-bf75-cf83bf6b3c91@posteo.de>

On Tue, Jan 16, 2018 at 12:12:33AM +0100, Max Schulze wrote:
> 
> > This indicates that option isn't the right driver for this for device.
> >
> > I think we should add a new simple driver for it instead, which reports
> > that modem control isn't (yet) supported (yes, your python script would
> > need to be updated). This can be extended into a "real" driver, should
> > we learn more about the protocol used.
> 
> Thank you. Tested with miniterm.py - it doesn't need any changes because
> no erroneous URB's are sent.

That's good. In your initial mail you mentioned that it was doing a
TIOCMBIS that was failing with the generic driver (which is essentially
the same thing as a "simple" driver).

> [  172.249297] usb_serial_simple 1-1.4:1.0: motorola_tetra converter
> detected
> [  172.249403] usb 1-1.4: motorola_tetra converter now attached to ttyUSB0
> [  172.249502] usb_serial_simple 1-1.4:1.1: motorola_tetra converter
> detected
> [  172.249578] usb 1-1.4: motorola_tetra converter now attached to ttyUSB1
> 
> > >From a7ab87acf85b67303e7bf606734176a365aae9cd Mon Sep 17 00:00:00 2001
> > From: Johan Hovold <johan@kernel.org>
> > Date: Fri, 12 Jan 2018 17:53:35 +0100
> > Subject: [PATCH] USB: serial: simple: add Motorola Tetra driver
> >
> > Add new Motorola Tetra (simple) driver for Motorola Solutions TETRA PEI
> > devices.
> >
> > D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
> > P:  Vendor=0cad ProdID=9011 Rev=24.16
> > S:  Manufacturer=Motorola Solutions Inc.
> > S:  Product=Motorola Solutions 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=(none)
> > I:  If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=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 <max.schulze@posteo.de>
> > Cc: stable <stable@vger.kernel.org>
> > Signed-off-by: Johan Hovold <johan@kernel.org>

> Works as-is. Tested in miniterm.py and minicom.
> 
> Tested-by: Max Schulze <max.schulze@posteo.de>

Thanks for testing!

Johan

             reply	other threads:[~2018-01-18  3:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-18  3:26 Johan Hovold [this message]
2018-01-18  3:26 ` [PATCH v3] USB: serial: option: add id for Motorola Solutions TETRA PEI Johan Hovold
  -- strict thread matches above, loose matches on Subject: below --
2018-01-15 23:12 [v3] " Max Schulze
2018-01-15 23:12 ` [PATCH v3] " Max Schulze
2018-01-12 17:19 [v3] " Johan Hovold
2018-01-12 17:19 ` [PATCH v3] " Johan Hovold
2018-01-12  9:29 [v3] " Max Schulze
2018-01-12  9:29 ` [PATCH v3] " Max Schulze

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180118032607.GF3286@localhost \
    --to=johan@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=max.schulze@posteo.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.