Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757464Ab3EOKyF (ORCPT ); Wed, 15 May 2013 06:54:05 -0400 Received: from mail-la0-f45.google.com ([209.85.215.45]:62152 "EHLO mail-la0-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751699Ab3EOKyE (ORCPT ); Wed, 15 May 2013 06:54:04 -0400 Message-ID: <51936946.3030507@iki.fi> Date: Wed, 15 May 2013 13:53:58 +0300 From: Tomi Valkeinen User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130404 Thunderbird/17.0.5 MIME-Version: 1.0 To: Kishon Vijay Abraham I CC: tony@atomide.com, linux@arm.linux.org.uk, linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, balbi@ti.com Subject: Re: [PATCH] ARM: OMAP4: change the device names in usb_bind_phy References: <1366697656-14315-1-git-send-email-kishon@ti.com> In-Reply-To: <1366697656-14315-1-git-send-email-kishon@ti.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1830 Lines: 48 On 23/04/13 09:14, Kishon Vijay Abraham I wrote: > After the device names are created using PLATFORM_DEVID_AUTO, the old > device names given in usb_bind_phy are no longer valid causing the musb > controller not to get the phy reference. Updated the usb_bind_phy with > the new device names to get MUSB functional in omap4 panda. > > Signed-off-by: Kishon Vijay Abraham I > --- > Tested in OMAP4 PANDA. > arch/arm/mach-omap2/board-4430sdp.c | 2 +- > arch/arm/mach-omap2/board-omap4panda.c | 2 +- > 2 files changed, 2 insertions(+), 2 deletions(-) > > diff --git a/arch/arm/mach-omap2/board-4430sdp.c b/arch/arm/mach-omap2/board-4430sdp.c > index 00d7290..56a9a4f 100644 > --- a/arch/arm/mach-omap2/board-4430sdp.c > +++ b/arch/arm/mach-omap2/board-4430sdp.c > @@ -730,7 +730,7 @@ static void __init omap_4430sdp_init(void) > omap4_sdp4430_wifi_init(); > omap4_twl6030_hsmmc_init(mmc); > > - usb_bind_phy("musb-hdrc.0.auto", 0, "omap-usb2.1.auto"); > + usb_bind_phy("musb-hdrc.2.auto", 0, "omap-usb2.3.auto"); > usb_musb_init(&musb_board_data); > > status = omap_ethernet_init(); I'm seeing [ 2.190155] unable to find transceiver [ 2.190155] HS USB OTG: no transceiver configured [ 2.190155] musb-hdrc musb-hdrc.0.auto: musb_init_controller failed with status -517 [ 2.207458] platform musb-hdrc.0.auto: Driver musb-hdrc requests probe deferral on 4430sdp with v3.10-rc1. Does that mean that the musb-hdrc.0.auto was indeed correct, and the new value of musb-hdrc.2.auto is not? The musb-hdrc id is wrong on overo also. Tomi -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/