Hi Alan,
I am again sending you the patch,
--- a/linux-3.6.1/drivers/usb/core/hub.c 2012-10-07 21:11:28.000000000
+0530
+++ b/linux-3.6.1/drivers/usb/core/hub.c 2012-10-31 11:37:26.760917272
+0530
@@ -1078,6 +1078,12 @@ static void hub_activate(struct usb_hub
clear_port_feature(hub->hdev, port1,
USB_PORT_FEAT_C_BH_PORT_RESET);
}
+ if (portchange & USB_PORT_STAT_C_RESET) {
+ need_debounce_delay = true;
+ clear_port_feature(hub->hdev, port1,
+ USB_PORT_FEAT_C_RESET);
+ }
+
/* We can forget about a "removed" device when there's a
* physical disconnect or the connect status changes.
*/
Let me know, in case of any issue / concern.
Thanks,
Bhavik Kothari
On Wednesday 31 October 2012 08:53 PM, Alan Stern wrote:
> On Wed, 31 Oct 2012, Bhavik Kothari wrote:
>
>> Hi Alan,
>>
>> Thanks for your inputs.
>>
>> As per your given instruction, we have modified a code and below is a patch,
>>
>>
>> --- a/linux-3.6.1/drivers/usb/core/hub.c 2012-10-07 21:11:28.000000000
>> +0530
>> +++ b/linux-3.6.1/drivers/usb/core/hub.c 2012-10-31 11:37:26.760917272
>> +0530
>> @@ -1078,6 +1078,12 @@ static void hub_activate(struct usb_hub
>> clear_port_feature(hub->hdev, port1,
>> USB_PORT_FEAT_C_BH_PORT_RESET);
>> }
>> + if (portchange & USB_PORT_STAT_C_RESET) {
>> + need_debounce_delay = true;
>> + clear_port_feature(hub->hdev, port1,
>> + USB_PORT_FEAT_C_RESET);
>> + }
>> +
>> /* We can forget about a "removed" device when there's a
>> * physical disconnect or the connect status changes.
>> */
>>
>>
>> We have created a patch using Linux 3.6.1 code. Now, we would like to
>> submit the patch.
>>
>> Please let us know, in case of any concern.
>
> Please follow the instructions in Documentation/SubmittingPatches.
>
> And be careful to use a mail program that doesn't damage the whitespace
> in the patch. In the patch above, the tab characters were converted to
> spaces. This makes the patch useless.
>
> Alan Stern
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
