UPSTREAM: usb: gadget: udc: core: Revise comments for USB ep enable/disable
The usb_ep_disable() and usb_ep_enable() routines are being widely used in atomic/interrupt context by function drivers. Hence, the statement about it being able to only run in process context may not be true. Add an explicit comment mentioning that it can be used in atomic context. Signed-off-by: Wesley Cheng <quic_wcheng@quicinc.com> Acked-by: Alan Stern <stern@rowland.harvard.edu> Bug: 204343836 (cherry picked from commit b0d5d2a71641bb50cada708cc8fdca946a837e9a) Change-Id: I1adb5d074fe2f9e33ebfdb30d335283c56bc7b39 Signed-off-by: Wesley Cheng <quic_wcheng@quicinc.com>
This commit is contained in:
parent
eb38c6d799
commit
c4ca993e0d
|
@ -89,7 +89,7 @@ EXPORT_SYMBOL_GPL(usb_ep_set_maxpacket_limit);
|
|||
* configurable, with more generic names like "ep-a". (remember that for
|
||||
* USB, "in" means "towards the USB host".)
|
||||
*
|
||||
* This routine must be called in process context.
|
||||
* This routine may be called in an atomic (interrupt) context.
|
||||
*
|
||||
* returns zero, or a negative error code.
|
||||
*/
|
||||
|
@ -134,7 +134,7 @@ EXPORT_SYMBOL_GPL(usb_ep_enable);
|
|||
* gadget drivers must call usb_ep_enable() again before queueing
|
||||
* requests to the endpoint.
|
||||
*
|
||||
* This routine must be called in process context.
|
||||
* This routine may be called in an atomic (interrupt) context.
|
||||
*
|
||||
* returns zero, or a negative error code.
|
||||
*/
|
||||
|
|
Loading…
Reference in New Issue