Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752767AbbBQUyW (ORCPT ); Tue, 17 Feb 2015 15:54:22 -0500 Received: from mout.kundenserver.de ([212.227.17.10]:61666 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751554AbbBQUyU (ORCPT ); Tue, 17 Feb 2015 15:54:20 -0500 From: Arnd Bergmann To: Arun Ramamurthy Cc: Kishon Vijay Abraham I , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , devicetree@vger.kernel.org, Jonathan Richardson , Scott Branden , Ray Jui , linux-arm-kernel@lists.infradead.org, bcm-kernel-feedback-list@broadcom.com, linux-kernel@vger.kernel.org, Dmitry Torokhov , Anatol Pomazau Subject: Re: [PATCH 1/2] phy: usbphy: Add dt documentation for Broadcom Cygnus USB PHY driver Date: Tue, 17 Feb 2015 21:53:36 +0100 Message-ID: <2797126.uqvyZJisPk@wuerfel> User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; ) In-Reply-To: <54E39DF1.50409@broadcom.com> References: <1424200821-16368-1-git-send-email-arun.ramamurthy@broadcom.com> <8242260.cl4QTECoeX@wuerfel> <54E39DF1.50409@broadcom.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V03:K0:qQa20hQkby6kSIkz2Mo+Hle92hCT6HWLt77VO92mfumoy0MFgyi kyMnm0y6BWTkjOCHnJspZgszTbE683iHPB6OQqiaB48aahq21ON0/R22C2szhSateoDQa2s LVnD3pyCASbY+6etBVt/Zk6Be+PvKcc+iSyzSDXgdHHLapqkZ5ChaPLs+s/+5dW5f/In2t+ EKM45w6Q0a2p6MWyX9zGw== X-UI-Out-Filterresults: notjunk:1; Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 973 Lines: 20 On Tuesday 17 February 2015 12:00:49 Arun Ramamurthy wrote: > Arnd, I patched the ehci and ohci driver to accept multiple phys so they > require different names and cannot both be "usb". That patch was > accepted by Alen Stern but I did not update the bindings documentation. > I will send out another patch for that. Could we go with the naming > scheme of "usb" + "p" + port number or do you have other suggestions? I don't have a good idea, but I think it would be best if the first phy could remain named "usb" for compatibility with the existing binding. What is the reason for having two phys in your case? Are these identical phy devices connected to a single controller or do they server different purposes? Arnd -- 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/