I believe I have found the root cause of this issue.
Before commit 6d23ee9caa6790aea047f9aca7f3c03cb8d96eb6
|_dwc2_hcd_suspend() did not end up calling dwc2_enter_hibernation(),
which was renamed to dwc2_enter_partial_power_down() in the same commit.
_dwc2_hcd_suspend() skipped |
>From 04fbf78e4e569bf872f1ffcb0a6f9b89569dc913 Mon Sep 17 00:00:00 2001
From: Hal Emmerich
Date: Thu, 19 Jul 2018 21:48:08 -0500
Subject: [PATCH] usb: dwc2: disable power_down on rockchip devices
The bug would let the usb controller enter partial power down,
which was formally known as
Replying to include I had with someone at synopsys, edited to remove
their info as I don't think their email is public.
> Hi Hal,
>
> Could you please apply this patch ([PATCH] usb: dwc2: Fix host exit from
> hibernation flow.) from linux-usb mailing list.
>
> Let me know if this patch doesn't
[1.] One line summary of the problem: Regression, USB devices not
recognized if plugged in after system boots
[2.] Full description of the problem/report:
If a usb device is plugged in before system begins booting into the
kernel, it will be recognized once boot completes.
However, if
Commit ff3f0789b3dc ("usb: dwc3: use BIT() macro where possible")
changed DWC3_DEPCFG_STREAM_EVENT_EN from bit 13 to bit 12.
Spotted this cleanup typo while looking at diffs between 4.9.35 and
4.14.16 for a separate issue.
Fixes: ff3f0789b3dc ("usb: dwc3: use BIT() macro where possible")
Based on USB2.0 Spec Section 11.12.5,
"If a hub has per-port power switching and per-port current limiting,
an over-current on one port may still cause the power on another port
to fall below specific minimums. In this case, the affected port is
placed in the Power-Off state and
Hi,
lemag...@gmail.com writes:
> From: Pierre Le Magourou
>
> We can't wait for END_OF_TRANSFER event in dwc3_gadget_ep_dequeue()
> because it can be called in an interruption context.
>
> TRBs are now cleared after the END_OF_TRANSFER completion, in the
> interrupt handler.
>
> Signed-off-by:
