From mboxrd@z Thu Jan 1 00:00:00 1970 From: kishon Subject: Re: [PATCH v1 0/6] USB: Add support for multiple PHYs of same type Date: Tue, 22 Jan 2013 21:15:01 +0530 Message-ID: <50FEB3FD.3050001@ti.com> References: <1358848694-20145-1-git-send-email-kishon@ti.com> <2D906ABA-71F2-4843-9DBE-F82527A1240A@dominion.thruhere.net> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <2D906ABA-71F2-4843-9DBE-F82527A1240A@dominion.thruhere.net> Sender: linux-kernel-owner@vger.kernel.org To: Koen Kooi Cc: tony@atomide.com, balbi@ti.com, linux@arm.linux.org.uk, eballetbo@gmail.com, javier@dowhile0.org, gregkh@linuxfoundation.org, linux-usb@vger.kernel.org, linux-arm-kernel@lists.infradead.org, "linux-omap@vger.kernel.org List" , linux-kernel@vger.kernel.org, devicetree-discuss@lists.ozlabs.org, Jason Kridner List-Id: devicetree@vger.kernel.org On Tuesday 22 January 2013 09:11 PM, Koen Kooi wrote: > > Op 22 jan. 2013, om 10:58 heeft Kishon Vijay Abraham I het volgende geschreven: > >> This patch series adds support for adding multiple PHY's (of same type). >> The binding information has to be present in the PHY library (otg.c) in >> order for it to return the appropriate PHY whenever the USB controller >> request for the PHY. So added a new API usb_bind_phy() to pass the binding >> information. This API should be called by platform specific initialization >> code. >> >> So the binding should be done something like >> usb_bind_phy("musb-hdrc.0.auto", 0, "omap-usb2.1.auto"); specifying the USB >> controller device name, index, and the PHY device name. >> I have done this binding for OMAP platforms, but it should be done for >> all the platforms. >> >> After this design, the phy can be got by passing the USB controller device >> pointer and the index. >> >> Developed this patch series on >> git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git xceiv >> after applying "usb: musb: add driver for control module" patch series >> and "ARM: dts: omap: add dt data for MUSB" >> >> Did basic enumeration testing in omap4 panda and omap3 beagle. > > With this patchset USB completely breaks on am33xx beaglebone, is that intended? Not really. Does am33xx makes use of omap2430.c? Which PHY does am33xx uses? Thanks Kishon