android/android_kernel_asus_sm8350
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

usb: musb: core: always try to recover from babble

Browse Source 
we can also have babble conditions with LS/FS
and we also want to recover in that case.

Because of that we will drop the check of HSMODE
and always try to run babble recovery.

Suggested-by: Bin Liu <b-liu@ti.com>
Signed-off-by: Felipe Balbi <balbi@ti.com>
This commit is contained in:
Felipe Balbi
2015-02-26 14:43:57 -06:00
parent 0244336f81
commit 34754dec8a
1 changed files with 6 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
drivers/usb/musb/musb_core.c
View File

@ -863,28 +863,18 @@ b_host:
if (int_usb & MUSB_INTR_RESET) {
handled = IRQ_HANDLED;
if (devctl & MUSB_DEVCTL_HM) {
u8 power = musb_readl(musb->mregs, MUSB_POWER);
/*
* Looks like non-HS BABBLE can be ignored, but
* HS BABBLE is an error condition.
*
* For HS the solution is to avoid babble in the first
* place and fix what caused BABBLE.
*
* When HS BABBLE happens what we can depends on which
* When BABBLE happens what we can depends on which
* platform MUSB is running, because some platforms
* implemented proprietary means for 'recovering' from
* Babble conditions. One such platform is AM335x. In
* most cases, however, the only thing we can do is drop
* the session.
* most cases, however, the only thing we can do is
* drop the session.
*/
if (power & MUSB_POWER_HSMODE) {
dev_err(musb->controller, "Babble\n");
dev_err(musb->controller, "Babble\n");
if (is_host_active(musb))
musb_recover_from_babble(musb);
}
if (is_host_active(musb))
musb_recover_from_babble(musb);
} else {
dev_dbg(musb->controller, "BUS RESET as %s\n",
usb_otg_state_string(musb->xceiv->otg->state));