| author | Ajay Kumar Gupta <ajay.gupta@ti.com> | |
| Thu, 11 Feb 2010 02:29:44 +0000 (18:29 -0800) | ||
| committer | Tony Lindgren <tony@atomide.com> | |
| Thu, 11 Feb 2010 02:29:44 +0000 (18:29 -0800) | ||
| commit | 765d8962a7030ca41e630087af9a691ad07e0557 | |
| tree | 4a41e06796062727dd49b0eda44353056ba39d9f | tree | snapshot (tar.xz tar.gz zip) |
| parent | 7e55d208fb2daac15a960aa7536c9b6bd3573f50 | commit | diff |
USB: musb: Add new fifo table for a OMAP3 errata
We have observed MSC data read corruption when USB LAN device is
also connected and it's interface is up.
Silicon team has confirmed an errata where in all the active
transfers should use FIFO space either in first 8K or next 8K.
So far we have observed the issue in above use case scenario.
As a workaround to it, adding a new FIFO config (5) fitting well
within first 8K which can be used for such use cases.
Signed-off-by: Ajay Kumar Gupta <ajay.gupta@ti.com>
Acked-by: Anand Gadiyar <gadiyar@ti.com>
Signed-off-by: Felipe Balbi <felipe.balbi@nokia.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Signed-off-by: Tony Lindgren <tony@atomide.com>
We have observed MSC data read corruption when USB LAN device is
also connected and it's interface is up.
Silicon team has confirmed an errata where in all the active
transfers should use FIFO space either in first 8K or next 8K.
So far we have observed the issue in above use case scenario.
As a workaround to it, adding a new FIFO config (5) fitting well
within first 8K which can be used for such use cases.
Signed-off-by: Ajay Kumar Gupta <ajay.gupta@ti.com>
Acked-by: Anand Gadiyar <gadiyar@ti.com>
Signed-off-by: Felipe Balbi <felipe.balbi@nokia.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Signed-off-by: Tony Lindgren <tony@atomide.com>
| drivers/usb/musb/musb_core.c | diff | blob | history |