| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <5465C75D.4070909@ti.com> Date: Fri, 14 Nov 2014 14:41:57 +0530 From: George Cherian <george.cherian@...com> To: Sebastian Andrzej Siewior <bigeasy@...utronix.de>, <balbi@...com> CC: <gregkh@...uxfoundation.org>, <linux-usb@...r.kernel.org>, <linux-kernel@...r.kernel.org> Subject: Re: [PATCH] usb: musb: core: Disable the Interrupts till BABBLE is fully handled On 11/14/2014 02:12 PM, Sebastian Andrzej Siewior wrote: > On 11/14/2014 09:24 AM, George Cherian wrote: >> Disable the MUSB interrupts till MUSB is recovered fully from BABBLE >> condition. There are chances that we could get multiple interrupts >> till the time the babble recover work gets scheduled. Sometimes >> this could even end up in an endless loop making MUSB itself unusable. > How do you trigger the babble error? Is this something that happens > during suspend resume, plugging / unplugging a device or randomly while > the device is used? I have never seen this error while device is successfully enumerated and while working fine. Mostly u get it when we connect/disconnect devices to HOST port. Normally I use the following for testing BABBLE - Especially when a fully loaded USB HUB getting connected to HOST port. - Or repeatedly load and unload musb_hdrc.ko with some device connected. If nothing of the above work you might be the lucky one to have a good board!!!! > > Sebastian > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists