public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Marek Belisko <marek@goldelico.com>
Cc: johan@kernel.org, gregkh@linuxfoundation.org, corbet@lwn.net,
	linux-usb@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, gta04-owner@goldelico.com,
	"H. Nikolaus Schaller" <hns@goldelico.com>
Subject: Re: [PATCH v2] Documentation usb serial: fixed how to provide vendor and product id
Date: Tue, 14 Apr 2015 09:30:50 +0200	[thread overview]
Message-ID: <20150414073050.GB24445@localhost> (raw)
In-Reply-To: <1428955767-23811-1-git-send-email-marek@goldelico.com>

On Mon, Apr 13, 2015 at 10:09:27PM +0200, Marek Belisko wrote:
> From: "H. Nikolaus Schaller" <hns@goldelico.com>
> 
> While trying to test a Cinterion GSM/GPS/3G module I had reconfigured
> the USB interface by mistake and therefore needed to run a different
> USB driver than CDC-ACM. It turned out that I need the "usbserial" driver.
> 
> This file is an official description how to use it: Documentation/usb/usb-serial.txt
> 
> But it is outdated. The parameters vendor= and product= are only available
> if compiled as a kernel module and have been superseded by a /sys interface.
> 
> Here was the solution:
> 
> https://bbs.archlinux.org/viewtopic.php?id=175499
> 
>   insmod usbserial vendor=0x#### product=0x####
> 
> becomes (first #### is vendor, second is product)
> 
>   modprobe usbserial
>   echo #### #### >/sys/bus/usb-serial/drivers/generic/new_id
> 
> This patch changes the documentation file to describe the modern variant.
> Please note that the old one still works (if compiled as module).
> 
> Signed-off-by: H. Nikolaus Schaller <hns@goldelico.com>
> Signed-off-by: Marek Belisko <marek@goldelico.com>
> ---
> 
> changes from v1:
> - add modern variant with /sys as preferred but also old one works so
>   keep it in documentation (was removed in first version which was not correct)

Thanks for the update. Much better.

>  Documentation/usb/usb-serial.txt | 11 +++++++----
>  1 file changed, 7 insertions(+), 4 deletions(-)
> 
> diff --git a/Documentation/usb/usb-serial.txt b/Documentation/usb/usb-serial.txt
> index 947fa62..3f31c96 100644
> --- a/Documentation/usb/usb-serial.txt
> +++ b/Documentation/usb/usb-serial.txt
> @@ -465,12 +465,15 @@ Generic Serial driver
>    device, and does not support any kind of device flow control. All that
>    is required of your device is that it has at least one bulk in endpoint,
>    or one bulk out endpoint. 
> -  
> -  To enable the generic driver to recognize your device, build the driver
> -  as a module and load it by the following invocation:
> -	insmod usbserial vendor=0x#### product=0x####
> +
> +  To enable the generic driver to recognize your device, provide
> +	echo #### #### >/sys/bus/usb-serial/drivers/generic/new_id
>    where the #### is replaced with the hex representation of your device's
>    vendor id and product id.

Could you use distinct symbols for vendor and product if (e.g. <vid>
and <pid>) to make it clear which is which?

> +  If the driver is compiled as a module, you can either
> +	modprobe usbserial

This isn't needed.

> +  or, you can also provide the parameters directly

This could be "you can also provide one id when loading the module".

> +	insmod usbserial vendor=0x#### product=0x####

Thanks,
Johan

  reply	other threads:[~2015-04-14  7:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-13 20:09 [PATCH v2] Documentation usb serial: fixed how to provide vendor and product id Marek Belisko
2015-04-14  7:30 ` Johan Hovold [this message]
2015-04-20 20:15 ` Marek Belisko
2015-04-21  7:47   ` Johan Hovold
2015-04-21 11:57     ` Bjørn Mork
2015-04-21 13:03       ` Johan Hovold
2015-05-07 15:45         ` Jonathan Corbet

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=20150414073050.GB24445@localhost \
    --to=johan@kernel.org \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=gta04-owner@goldelico.com \
    --cc=hns@goldelico.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=marek@goldelico.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox