From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751697Ab3FNFr1 (ORCPT ); Fri, 14 Jun 2013 01:47:27 -0400 Received: from mho-02-ewr.mailhop.org ([204.13.248.72]:34286 "EHLO mho-02-ewr.mailhop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751224Ab3FNFrZ (ORCPT ); Fri, 14 Jun 2013 01:47:25 -0400 X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 50.131.214.131 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX18St9sx9txV96ardkDaJec6 Date: Thu, 13 Jun 2013 22:47:20 -0700 From: Tony Lindgren To: Kishon Vijay Abraham I Cc: Tomi Valkeinen , balbi@ti.com, linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org, linux@arm.linux.org.uk, eballetbo@gmail.com, javier@dowhile0.org, gregkh@linuxfoundation.org Subject: Re: [RFC PATCH 1/4] arm: omap: Add phy binding info for musb in plat data Message-ID: <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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <51BAABB0.5060107@ti.com> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * 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. Regards, Tony