public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jef Driesen <jefdriesen@telenet.be>
To: Greg KH <greg@kroah.com>
Cc: Robert Lukassen <Robert.Lukassen@tomtom.com>,
	David Brownell <dbrownell@users.sourceforge.net>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] USB: g_serial: Allow to override the default VID/PID
Date: Sun, 21 Nov 2010 00:03:27 +0100	[thread overview]
Message-ID: <4CE853BF.80504@telenet.be> (raw)
In-Reply-To: <20101120001247.GB17421@kroah.com>

On 20/11/10 01:12, Greg KH wrote:
> On Sat, Nov 20, 2010 at 12:32:34AM +0100, Jef Driesen wrote:
>> Override the default VID/PID if custom values are supplied through the
>> idVendor and idProduct kernel module parameters.
>>
>> Signed-off-by: Jef Driesen<jefdriesen@telenet.be>
>
> So this patch resolves the bug found in
> 1ab83238740ff1e1773d5c13ecac43c60cf4aec4 which showed up in .35-rc1,
> right?

Yes, although I'm really sure it is the best way to fix the problem. The way I 
understand this code is that before that commit, the 
idVendor/idProduct/bcdDevice module parameters where set after the bind(). Thus 
whatever was set as the default there got replaced with the values of the module 
parameters. Exactly what I would consider the correct behavior. After the 
commit, they get set before bind(), where they are changed back to the hardcoded 
values, which I think is wrong. My patch sets them back to the right values, but 
maybe it makes more sense to not set the default values in the first place (if 
there are already values in place of course). But I didn't knew how to 
accomplish that.

There might be similar problems for the other gadget drivers as well. I haven't 
checked that.

>> ---
>>   drivers/usb/gadget/serial.c |    5 +++++
>>   1 files changed, 5 insertions(+), 0 deletions(-)
>>
>> diff --git a/drivers/usb/gadget/serial.c b/drivers/usb/gadget/serial.c
>> index f46a609..77b410e 100644
>> --- a/drivers/usb/gadget/serial.c
>> +++ b/drivers/usb/gadget/serial.c
>> @@ -271,6 +271,11 @@ static int __init init(void)
>>   	}
>>   	strings_dev[STRING_DESCRIPTION_IDX].s = serial_config_driver.label;
>>
>> +	if (idVendor)
>> +		device_desc.idVendor = idVendor;
>> +	if (idProduct)
>> +		device_desc.idProduct = idProduct;
>> +
>>   	return usb_composite_register(&gserial_driver);
>>   }
>>   module_init(init);
>> --
>> 1.7.1

  reply	other threads:[~2010-11-20 23:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4CE6F807.1090607@telenet.be>
2010-11-19 23:32 ` [PATCH] USB: g_serial: Allow to override the default VID/PID Jef Driesen
2010-11-20  0:12   ` Greg KH
2010-11-20 23:03     ` Jef Driesen [this message]
2010-11-22 10:20       ` Robert Lukassen
2010-11-30 17:46         ` Greg KH
2010-12-03 22:09           ` Jef Driesen
2010-12-06  8:09             ` Robert Lukassen
2010-12-15  7:57               ` Jef Driesen
2010-12-17  0:02                 ` Greg KH

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=4CE853BF.80504@telenet.be \
    --to=jefdriesen@telenet.be \
    --cc=Robert.Lukassen@tomtom.com \
    --cc=dbrownell@users.sourceforge.net \
    --cc=greg@kroah.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    /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