linux-kernel - Re: [PATCH] usb: musb: core: Disable the Interrupts till BABBLE is fully handled

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <54743CCE.20202@linutronix.de>
Date:	Tue, 25 Nov 2014 09:24:46 +0100
From:	Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To:	balbi@...com
CC:	George Cherian <george.cherian@...com>, 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/25/2014 02:09 AM, Felipe Balbi wrote:
> 
>> I *think* for some reason the host did not really receive ep0
>> set_config request as planned. And device's answer is probably then
>> interpreted as data which is not expected (as Felipe said "device side
>> tries to move data without the host asking for anything").
> 
> that's definitely a bug, unfortunately I can't think of any Erratum
> right now.

maybe there will be a new one :)

>>>> That's certainly babble :-)
>>>
>>> Certainly! But musb shouldn't fall over or lock up because of it,
>>> should it?
>>
>> No and the patch fixes the issue. The strange thing is that it only
>> happens on the same device. Not if you connect host<->device with two
>> boards.
> 
> probably some crap going on within the interconnect when both instances
> are used.
Either that or something is synchronized since both instances use
probably the same clock source. But there is definitely something
switched off since it does not happen without PM enabled.

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/