On 8/9/2022 6:08 PM, Thinh Nguyen wrote:
On 8/9/2022, Elson Serrao wrote:
On 8/4/2022 6:26 PM, Thinh Nguyen wrote:
On 8/4/2022, Elson Serrao wrote:
On 8/2/2022 4:51 PM, Thinh Nguyen wrote:
On 8/2/2022, Elson Roy Serrao wrote:
An interface which is in function suspend state has to send a function
wakeup notification to the host in case it needs to initate any data
transfer. One notable difference between this and the existing remote
wakeup mechanism is that this can be called per-interface, and a UDC
would need to know the particular interface number to convey in its
Device Notification transaction packet. Hence, we need to introduce
a new callback in the gadget_ops structure that UDC device drivers
can implement. Similarly add a convenience function in the composite
driver which function drivers can call. Add support to handle such
requests in the composite layer and invoke the gadget op.
Sending the function wake notification should be done in the controller
driver. The controller driver knows when is the proper link state
(U0/ON) the device is in and would notify the host then.
What we need to add in the usb_gadget is whether the device is remote
wakeup capable. Something like a flag usb_gadget->rw_capable.
We would also need some functions like
usb_gadget_enable_remote_wakeup()
and usb_gadget_disable_remote_wakeup() for the gadget driver to notify
the controller driver when it checks against USB_CONFIG_ATT_WAKEUP in
the bmAttributes configuration.
BR,
Thinh
If we handle this in controller driver, then it would fail to get the
right interface id when multiple functions have to send function wake
notification. As per USB3.0 spec (below snippets) a function can be
independently placed into function suspend state within a composite
device and each function in function suspend state has to send a
function wake notification to exit.
USB 3.0 Spec Section 9.2.5.3
"A function may be placed into Function Suspend independently of other
functions within a composite device"
USB 3.0 Spec Section 9.2.5.4
"A function may signal that it wants to exit from Function Suspend by
sending a Function Wake Notification to the host if it is enabled for
function remote wakeup. This applies to single function devices as
well as multiple function ( i.e., composite) devices. If the link is in
a non-U0 state, then the device must transition the link to U0 prior
to sending the remote wake message. If a remote wake event occurs in
multiple functions, each function shall send a Function Wake
Notification"
Ok, so the issue here is adding the ability to pass the interface number
to the controller driver when sending the device notification function
wakeup right? Sounds like the callback should be
send_wakeup_notification(gadget, func_id) instead.
As for remote wakeup, the spec states that "If remote wake event occurs
in multiple functions, each function shall send a Function Wake
Notification."
The SET_FEATURE(FUNCTION_SUSPEND) does not necessarily mean the host
will put the device in Suspend State for a remote wake event to occur.
It only places the function in Function Suspend. However often the host
will put the device in suspend after this. The dwc3 driver can track if
the host puts the device in suspend state and what interfaces are armed
for remote wakeup. If a remote wakeup event occurs, the dwc3 driver can
send Function Wake Notification for each function armed with remote
wakeup.
Please correct me if I'm wrong.
Also, make sure that device remote wakeup will still work for highspeed
(not function remote wakeup). I see this check which doesn't look right
in one of your patches:
+ if (g->speed < USB_SPEED_SUPER && !dwc->is_remote_wakeup_enabled)
+ dev_err(dwc->dev, "%s:remote wakeup not supported\n", __func__);
+ ret = -EPERM;
+ goto out;
+ }
Thanks,
Thinh
For superspeed capable devices, when a function is in suspend state and
wants to
initiate a resume, it has to send a function wake notification to the
host irrespective
of whether the device is in SUSPEND or not. Like you mentioned the
device need not be in
suspend state when a function is suspended. If the device is in suspend,
then first the
controller driver has to transition the link to U0 state before sending
function wake notification.
Was I incorrect? I'm not clear on the point of reiteration above.
Note that the DEVICE_REMOTE_WAKEUP feature is ignored for super-speed
devices and they
We're still talking about Enhanced Super Speed here.
are by default remote wakeup capable if any function within the device
is armed for
function remote wakeup.
What you're saying is if the host arms the function for remote wakeup,
then the device is remote capable.
However, the important point here is that the host only arms for remote
wakeup _if_ the device is remote wakeup capable. That needs to be checked.
Yes. The device would have advertised its remote wakeup capability
during enumeration stage itself based on which host sets
SET_FEATURE(FUNCTION_SUSPEND) RW option.
So in my current implementation when the host sends a function suspend
SET_FEATURE(FUNCTION_SUSPEND),
the device delegates it to the respective function driver. There we
inspect if it is capable
of initiating a function remote wakeup. If it is, then when a remote
wakeup event
occurs (in my current implementation when TCP/IP layer wants to send
data to the host. patch#5) then
we trigger a function wakeup by calling usb_gadget_func_wakeup(gadget,
id) callback. Controller driver then
checks if the device is in suspend or not. If it is in suspend, it first
brings the device to U0 state
"brings the device to U0 state" means the device initiates remote wakeup
here.
and then sends a function wake notification (via
dwc3_send_gadget_generic_command() API) only after an
So now the dwc3 tracks which interface(s) were armed for remote here?
I don't recall seeing it in your patches. Did you handle and send device
notification for all the functions armed with remote wakeup after device
wakeup?
That task is delegated to function driver. In patch#5 the
function/composite layer sends wakeup notification only if it is armed
for func remote wakeup.
func_wakeup_allowed flag serves this purpose for f_ecm function driver.
This flag is set based on SET_FEATURE(FUNCTION_SUSPEND) packet (which in
turn depends on the remote wakeup capability advertised by the device in
bmAttributes like mentioned above).
U0 event has occurred. If the device is not in suspend then it directly
sends function wake notification
to the host. Once the host receives the function wake notification it
sends a SET_FEATURE(FUNCTION_SUSPEND)
with suspend bit (BIT 0) reset to signal function resume. The controller
driver upon receiving this packet
delegates to the respective function driver. Note that at this point the
device is in U0 state but some other
We can't assume that the device is in U0 state. There's also no
mechanism in your change to know that either.
function within the device may still be in suspend state (if more than
one function was put to suspend state).
So the only way to exit from function suspend is via function resume
which is independent of device suspend/resume.
Also the task of finding the interface id is done by composite driver
because most function drivers have
a transport layer and this layer is the one responsible for issuing a
function remote wakeup and
this has no direct reference to interface id. For example u_ether
transport layer can have either f_ecm or f_rndis
as its underlying channel and u_ether has no knowledge of the interface
id/function driver it is using.
For high speed devices there is no concept of function suspend and there
is only device suspend. The ability
of a device to send a remote wakeup to exit from suspend is dictated by
DEVICE_REMOTE_WAKEUP feature selector.
The below snippet controls this aspect and sends remote wakeup for high
speed devices only if they are remote wakeup capable.
dwc->is_remote_wakeup_enabled flag is set when DEVICE_REMOTE_WAKEUP is
received.
The flag "is_remote_wakeup_enabled" implies that it applies for both
device remote wakeup and function remote wakeup. If it only meant for
function remote wakeup, then rename it. But I think you can use the same
flag for both scenarios.
The flag is_remote_wakeup_enabled is only meant for device remote wakeup
and is only used in High Speed. In my implementation function remote
wakeup flag is at function level which is set in the function driver
based on whether the function is armed for remote wakeup. The
function/composite layer would send wakeup notification only if it is
armed for remote wakeup.
Below snippet from patch#5
Set the function_wakeup_allowed flag based on USB_INTRF_FUNC_SUSPEND_RW
option
+static int ecm_func_suspend(struct usb_function *f, u8 options)
+{
+ bool func_wakeup_allowed;
+ struct f_ecm *ecm = func_to_ecm(f);
+ struct usb_composite_dev *cdev = ecm->port.func.config->cdev;
+
+ DBG(cdev, "func susp %u cmd\n", options);
+
+ func_wakeup_allowed = !!(options & (USB_INTRF_FUNC_SUSPEND_RW >> 8));
Send wakeup notification only if func_wakeup_allowed flag is set.
+ if (!port->func_wakeup_allowed) {
+ DBG(port->ioport, "Function wakeup not allowed\n");
+ return -EOPNOTSUPP;
+ }
+ ret = usb_func_wakeup(func);
+ if (g->speed < USB_SPEED_SUPER && !dwc->is_remote_wakeup_enabled)
+ dev_err(dwc->dev, "%s:remote wakeup not supported\n", __func__);
+ ret = -EPERM;
Also, don't use -EPERM. Use -EINVAL.
Done.
+ goto out;
+ }
Please let me know your thoughts on this approach. I will address your
other comments and rectify the patches accordingly.
To summarize the points:
1) The host only arms function remote wakeup if the device is capable of
remote wakeup (check USB_CONFIG_ATT_WAKEUP in bmAttributes and hardware
capability)
2) If the device is in suspend, the device can do remote wakeup (through
LFPS handshake) if the function is armed for remote wakeup (through
SET_FEATURE(FUNC_SUSPEND)).
3) If the link transitions to U0 after the device triggering a remote
wakeup, the device will also send device notification function wake for
all the interfaces armed with remote wakeup.
4) If the device is not in suspend, the device can send device
notification function wake if it's in U0.
Now, remote wakeup and function wake device notification are 2 separate
operations. We have the usb_gadget_ops->wakeup() for remote wakeup. I
suggested to maybe add usb_gadget_ops->send_wakeup_notification(gadget,
intf_id) for the device notification. What you did was combining both
operations in usb_gadget_ops->func_wakeup(). That may only work for
point 4) (assuming you fix the U0 check), but not point 3).
Thank you for your feedback and summary. I will rename func_wakeup to
send_wakeup_notification to better align with the approach. The reason I
have combined remote_wakeup and function wake notification in
usb_gadget_ops->func_wakeup() is because since the implementation is at
function/composite level it has no knowledge on the link state. So I
have delegated that task to controller driver to handle the notification
accordingly. That is do a LFPS handshake first if the device is
suspended and then send notification (explained below). But we can
definitely separate this by adding an additional flag in the composite
layer to set the link state based on the gadget suspend callback called
when U3 SUSPEND interrupt is received. Let me know if you feel
separating the two is a better approach.
I have explained below, how the 4 points you mentioned are handled in my
current implementation.
The function driver will send a wakeup notification only if it is armed
for remote wakeup.
patch#5
+ if (!port->func_wakeup_allowed) {
+ DBG(port->ioport, "Function wakeup not allowed\n");
+ return -EOPNOTSUPP;
+ }
+ ret = usb_func_wakeup(func);
+ if (ret)
+ port->is_wakeup_pending = true;
If the device is in suspend, we do a LFPS handshake first and return
-EAGAIN to composite layer which will set the is_wakeup_pending flag.
Patch#3
+static int dwc3_gadget_func_wakeup(struct usb_gadget *g, int interface_id)
+{
+ int ret = 0;
+ u32 reg;
+ struct dwc3 *dwc = gadget_to_dwc(g);
+
+ reg = dwc3_readl(dwc->regs, DWC3_DSTS);
+
+ /*
+ * If the link is in LPM, first bring the link to U0
+ * before triggering function wakeup. Ideally this
+ * needs to be expanded to other LPMs as well in
+ * addition to U3
+ */
+ if (DWC3_DSTS_USBLNKST(reg) == DWC3_LINK_STATE_U3) {
+ dwc3_gadget_wakeup(g);
+ return -EAGAIN;
+ }
The above should take care of Point 2.
After triggering a remote wakeup in Point 2, if the link transitions to
U0 then we will receive a U0 link state event for the same and that
would trigger a gadget_resume callback to inform the composite layer
that device has resumed. As soon as the function/composite layer gets
this info it will re-send the wakeup notification to the controller
driver based on the is_wakeup_pending flag
linksts_change_interrupt() in Patch#1
+ case DWC3_LINK_STATE_U0:
+ if (dwc->is_gadget_wakeup) {
+ linksts_change_events_set(dwc, false);
+ dwc3_resume_gadget(dwc);
+ dwc->is_gadget_wakeup = false;
+ }
+ break;
u_ether resume callback in Patch#5
+ if (func_suspend) {
+ if (link->is_wakeup_pending) {
+ usb_func_wakeup(func);
+ link->is_wakeup_pending = false;
+ }
The above should take care of Point 3.
For Point 4 like you mentioned I will add U0 check instead of U3 check.
Point 1 would have resolved in enumeration stage itself (bmAttributes in
config descriptor) based on which the host sets the
USB_INTRF_FUNC_SUSPEND_RW option in the SET_FEATURE(FUNCTION_SUSPEND)
packet. Based on this option the function/composite driver will set
func_wakeup_allowed flag arming it for remote_wakeup
+static int ecm_func_suspend(struct usb_function *f, u8 options)
+{
+ bool func_wakeup_allowed;
+ struct f_ecm *ecm = func_to_ecm(f);
+ struct usb_composite_dev *cdev = ecm->port.func.config->cdev;
+
+ DBG(cdev, "func susp %u cmd\n", options);
+
+ func_wakeup_allowed = !!(options & (USB_INTRF_FUNC_SUSPEND_RW >> 8));
Do we need any additional checks for Point 1 ? Please let me know if my
understanding is incorrect here.
To be able to do 3), you can teach the composite layer _when_ to send
device notification function wake and for what functions. This can be
retry sending the notification until send_wakeup_notification() succeed?
I suggested to do that in dwc3 driver to avoid having to add the logic
in composite layer as I think it is simpler in dwc3. However, the
downside is that other UDCs have to handle it like dwc3 also.
Now that I think about it again, it maybe better to do it in the
composite driver for the long run. If you want to handle this in the
composite layer, please document and design the mechanism to handle all
the points above. >
Thanks,
Thinh
Please let me know if this implementation fails to cover the 4 points
you mentioned or any other rectification needed to handle these points.
Thanks & Regards
Elson
