From: tomi.valkeinen@ti.com (Tomi Valkeinen) Date: Fri, 14 Jun 2013 09:36:26 +0300 Subject: [RFC PATCH 1/4] arm: omap: Add phy binding info for musb in plat data In-Reply-To: <20130614054720.GL8164@atomide.com> References: <1368796954-3499-1-git-send-email-kishon@ti.com> <51A43E0A.8090201@ti.com> <51B9C3B6.1080707@ti.com> <51BAABB0.5060107@ti.com> <20130614054720.GL8164@atomide.com> Message-ID: <51BAB9EA.5090805@ti.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 14/06/13 08:47, Tony Lindgren wrote: > * Kishon Vijay Abraham I [130613 22:41]: >> Hi, >> >> On Thursday 13 June 2013 06:35 PM, Tomi Valkeinen wrote: >>> Hi, >>> >>> On 28/05/13 08:18, Kishon Vijay Abraham I wrote: >>>> Hi Tony, >>>> >>>> On Friday 17 May 2013 06:52 PM, Kishon Vijay Abraham I wrote: >>>>> In order for controllers to get PHY in case of non dt boot, the phy >>>>> binding information (phy label) should be added in the platform >>>>> data of the controller. >>>> >>>> This series would be needed to get MUSB working in OMAP3 boards for >>>> non-dt boot case. Do you think this is good enough to go in this rc cycle? >>> >>> Did this or some other solution go forward? I'm still unable to boot >>> with usb-gadget-ethernet with v3.10-rc5. >> >> No. I think Tony is ok to take this only during next merge window. > > Yes I'll apply them to omap-for-v3.11/fixes-non-critical. We really > should have basic functionaly tested and working always before the > merge window so we only need to do minimal fixes during the -rc cycle. I'm mostly interested in the USB gadget ethernet for the boards I have, but if I'm not mistaken, all USB gadget support for many OMAP boards is broken in v3.10. Shouldn't that be fixed, no matter if it's a minimal fix or not? Or is there some other, more minimal, way to fix this? Tomi -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 901 bytes Desc: OpenPGP digital signature URL: