Hi George,
On 05/13/2014 02:57 PM, George Cherian wrote:
> I never enabled the MUSB_BABBLE_SW_SESSION_CTRL in the MUSB_BABBLE_CTL reg.
> can you try with the following patch.
>
> diff --git a/drivers/usb/musb/musb_dsps.c b/drivers/usb/musb/musb_dsps.c
> index 1ae6681..1160cd1 100644
> --- a/drivers/usb/musb/musb_dsps.c
> +++ b/drivers/usb/musb/musb_dsps.c
> @@ -477,8 +477,11 @@ static int dsps_musb_init(struct musb *musb)
> * logic enabled.
> */
> val = dsps_readb(musb->mregs, MUSB_BABBLE_CTL);
> - if (val == MUSB_BABBLE_RCV_DISABLE)
> + if (val == MUSB_BABBLE_RCV_DISABLE) {
> glue->sw_babble_enabled = true;
> + val |= MUSB_BABBLE_SW_SESSION_CTRL;
> + dsps_writeb(musb->mregs, MUSB_BABBLE_CTL, val);
> + }
>
> ret = dsps_musb_dbg_init(musb, glue);
> if (ret)
MUSB_BABBLE_STUCK_J still remains unset, so I get the same result as
without the patch: a full glue reset is conducted. Do I get you right
that you expect MUSB_BABBLE_STUCK_J to be set in babble conditions when
MUSB_BABBLE_SW_SESSION_CTRL is set?
[ 19.672373] CAUTION: musb: Babble Interrupt Occurred
[ 19.677776] musb_stage0_irq 789: unhandled DISCONNECT transition
(a_wait_bcon)
[ 19.685815] usb 1-1: USB disconnect, device number 3
[ 19.769720] musb-hdrc musb-hdrc.0.auto: babble: MUSB_BABBLE_CTL value 44
[ 19.776765] musb-hdrc musb-hdrc.0.auto: STUCK_J is reset
I don't quite follow, especially as I lack documentation of the IP core.
How do you test babble errors, is there any way to force them to happen
reliably?
Anyway, the full glue layer solves this rare condition quite well for
me. Is there any downside of this?
Daniel
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
