Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753092AbbBYR1k (ORCPT ); Wed, 25 Feb 2015 12:27:40 -0500 Received: from mail-qa0-f42.google.com ([209.85.216.42]:49342 "EHLO mail-qa0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752759AbbBYR1h (ORCPT ); Wed, 25 Feb 2015 12:27:37 -0500 MIME-Version: 1.0 In-Reply-To: <20150225160110.GA26610@ulmo> References: <1416874644-12070-1-git-send-email-abrestic@chromium.org> <20150225160110.GA26610@ulmo> Date: Wed, 25 Feb 2015 09:27:36 -0800 X-Google-Sender-Auth: yvGq1dO7jS_tPH8gNwqdHAoa0cA Message-ID: Subject: Re: [PATCH V6 00/12] Tegra xHCI support From: Andrew Bresticker To: Thierry Reding Cc: Stephen Warren , Alexandre Courbot , "linux-tegra@vger.kernel.org" , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Jassi Brar , Linus Walleij , Greg Kroah-Hartman , Mathias Nyman , Grant Likely , Alan Stern , Arnd Bergmann , Olof Johansson , Kishon Vijay Abraham I , Felipe Balbi , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "linux-usb@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1508 Lines: 36 Hi Thierry, > Sorry for taking so awfully long to look at this. I've spent some time > looking at various pieces of documentation and I concluded that > representing the port assignment as muxing options doesn't seem right > after all. Instead I've come up with an alternate proposal (attached). > Could you take a look and see if that sounds reasonable to you? Thanks for taking a look at this. I've been meaning to pick this series back up, but haven't had quite enough bandwidth lately. This all looks good to me, just one comment below: > +PHY nodes: > +---------- > + > +An optional child node named "phys" can contain nodes describing additional > +properties of each PHY. Only USB3 and UTMI PHYs can be complemented in this > +way, in which case the name of each node must match one of the following: > + > + usb3-0, usb3-1, utmi-0, utmi-1, utmi-2 > + > +Required properties for USB3 PHYs: > +- nvidia,lanes: specifies the name of the lane that this USB3 PHY uses > +- nvidia,port: specifies the number of the USB2 port that is used for this > + USB3 PHY > + > +Optional properties for UTMI PHYs: > +- vbus-supply: regulator providing the VBUS voltage for the UTMI pad What about the HSIC PHYs? Shouldn't they be represented as PHY nodes as well? -- 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/