Bug#773400: Cause of USB problem on beablebone black.

2015-05-25 Thread Lennart Sorensen 
On Sun, May 24, 2015 at 04:09:30PM +0100, Ben Hutchings wrote:
 Thanks for the analysis.  There were a few more related patches, but
 this got me on the right track.  I've applied them for 3.16.7-ckt11-1.

Great.  I imagine some beaglebone users will be pleased.

Using the 4.0 image from sid seems to work fine, so the patches at least
seem to work.

-- 
Len Sorensen


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150525180613.ga6...@csclub.uwaterloo.ca

Bug#773400: Cause of USB problem on beablebone black.

2015-05-24 Thread Ben Hutchings 
On Thu, 2015-05-21 at 16:46 -0400, Lennart Sorensen wrote:
 The config option CONFIG_USB_MUSB_TUSB6010 breaks the musb driver on
 anything that is not the tusb 6010, including the beaglebone.
 
 Turning off that option in the kernel config should fix it, or including
 the upstream patches that make it runtime detect what type of device it
 is on would work too.
 
 The upstream patches I believe are:
 
 9d506fc6d2cdafdec5ce605036f5eeec9fd59657 usb: musb: Populate new IO functions 
 for tusb6010
 
 1b40fc57a517878cf4c2e16ce29cc9a066dc1064 usb: musb: Change to use new IO 
 access
 
 d026e9c76aac3632af174cf02d5c94defa5e6026 usb: musb: Change end point 
 selection to use new IO access
 
 8a77f05aa39be879535f22a9757e703581fa1392 usb: musb: Pass fifo_mode in 
 platform data
 
 If the kernel package in jessie was to include those patches, or just
 change the config option on arm, it ought to fix the beaglebone's usb
 problems.

Thanks for the analysis.  There were a few more related patches, but
this got me on the right track.  I've applied them for 3.16.7-ckt11-1.

Ben.

-- 
Ben Hutchings
Experience is what causes a person to make new mistakes instead of old ones.


signature.asc
Description: This is a digitally signed message part