Hi, On Wed, Jun 08, 2011 at 05:12:02PM +0300, yauheni.kaliuta@xxxxxxxxx wrote: > From: Yauheni Kaliuta <yauheni.kaliuta@xxxxxxxxx> > > It fixes MUSB's hardware feature, that it doesn't actually flush FIFOs, > when TXPKTRDY flag was set before and we are flushing setting both > FLUSHFIFO and TXPKTRDY. > > The specification says about FLUSHFIFO, that it "May be set simultaneously > with TxPktRdy to abort the packet that is currently being loaded into the > FIFO". This is a situation, where TXPKTRDY hasn't been set yet, but some > data already loaded into the fifo. It looks, that if TXPKTRDY has been > set before and there is no loading in progress but we set FLUSHFIFO with > the TXPKTRDY, controller tries to use the same logic to abort loading > and as the result just does nothing (because there is no loading in progress) > > Signed-off-by: Yauheni Kaliuta <yauheni.kaliuta@xxxxxxxxx> applied to fixes branch, thanks -- balbi
Attachment:
signature.asc
Description: Digital signature
