From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hans de Goede Date: Fri, 19 Jun 2015 15:14:16 +0200 Subject: [U-Boot] [PATCH 00/22] Convert musb host mode code to the device-model In-Reply-To: References: <1434569645-30322-1-git-send-email-hdegoede@redhat.com> Message-ID: <558415A8.2030600@redhat.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hi, On 19-06-15 15:10, Simon Glass wrote: > Hi Hans, > > On 17 June 2015 at 13:33, Hans de Goede wrote: >> >> Hi Marek and Simon, >> >> This series started out with the idea that it would be a nice small project >> for the weekend, but it turned out to be a bit more work... >> >> The main purpose of this series is to convert the musb host mode code to the >> device-model this has also resulted in various usb fixes / cleanups / >> reworking to make this possible, both in the generic usb code as well as in >> the device model usb code. >> >> Given that this touches both, I think it is probably best to merge the >> first 15 patches through Simon's tree like we did last time, then once those >> are place I can merge the sunxi bits. Note this is intended for v2015.10 >> (ofcourse). >> >> Note that this series is useful for a bunch more boards then just the >> single one the last patch updates to use musb + ehci + ohci, but that is >> the one I've been testing with other defconfig-s will be updated with >> followup patches. >> >> Please review. > > Thanks for putting this together. Actually I'm not sure what musb is. > Can you explain what it is used for - it seems to be referred to as a > new version of something else. Why do we have musb and non-musb? Is > there a README somewhere I could read? p.s. As for there being both a drivers/usb/musb and a driver/usb/musb-new directoyry, I believe that they both are drivers for the same hardware, but not all boards have been ported to musb-new yet. musb-new is derived from recent kernel code for the musb controller. Regards, Hans > > Regards, > Simon >