[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.44L0.1512211053330.22031-100000@netrider.rowland.org>
Date: Mon, 21 Dec 2015 10:56:04 -0500 (EST)
From: Alan Stern <stern@...land.harvard.edu>
To: Vikas Bansal <vikas.bansal@...sung.com>
cc: oneukum@...e.de, <netdev@...r.kernel.org>,
<linux-usb@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<sumit.batra@...sung.com>
Subject: Re: [PATCH] Adding Reset resume support for CDC-EEM driver.
On Mon, 21 Dec 2015, Vikas Bansal wrote:
> Pre-Condition
> At the time of reset resume of a USB device, both self and bus powered devices might go to a low power state or power off state depending on the acceptable suspend time power of the system.
> In case the device experiences a power glitch or completely powers off during suspend-resume, the device will lose its internal state and hence it'll again need a set interface from class driver on reset resume operation.
>
> Issue
> So far our experiments were based on a USB gadget working on cdc_eem protocol.
> We have seen that device is unable to continue the packet transfer on bulk endpoints after the reset resume operation.
>
> Solution
> We have added a .reset_resume function for cdc_eem protocol which sends a set interface command on the Control endpoint. And calls the existing usbnet_resume thereafter
You know, the USB core already issues a Set-Interface request on the
control endpoint whenever a reset-resume occurs (unless the interface
was using altsetting 0 beforehand). Issuing another Set-Interface
shouldn't make any difference.
Alan Stern
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists