From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752778AbbBRPPR (ORCPT ); Wed, 18 Feb 2015 10:15:17 -0500 Received: from mout.kundenserver.de ([212.227.126.131]:62944 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751646AbbBRPPO (ORCPT ); Wed, 18 Feb 2015 10:15:14 -0500 From: Arnd Bergmann To: linux-arm-kernel@lists.infradead.org Cc: Arun Ramamurthy , Mark Rutland , devicetree@vger.kernel.org, Scott Branden , Pawel Moll , Ian Campbell , Ray Jui , linux-kernel@vger.kernel.org, Kishon Vijay Abraham I , Jonathan Richardson , Rob Herring , bcm-kernel-feedback-list@broadcom.com, Dmitry Torokhov , Kumar Gala , Anatol Pomazau , stern@rowland.harvard.edu Subject: Re: [PATCH 1/2] phy: usbphy: Add dt documentation for Broadcom Cygnus USB PHY driver Date: Wed, 18 Feb 2015 16:15:01 +0100 Message-ID: <11865413.8NsXkQ6AUR@wuerfel> User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; ) In-Reply-To: <54E3AD2E.8050902@broadcom.com> References: <1424200821-16368-1-git-send-email-arun.ramamurthy@broadcom.com> <2797126.uqvyZJisPk@wuerfel> <54E3AD2E.8050902@broadcom.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V03:K0:Auk1rlNnnSjKQl1nXwjI6IDofqL5//MsgjGLQ62SHwq63KH8hsS /FYF+LxExhkLwUi5KJkhpjeIBkgMRp7zKuHLqiwtSV3w/unjMC8/2Pp7GigGRPVj4TyPdZe A1o69k934cO4EegMWpW2HQHvD104gw0soKYx59PC9MYzb3l6TZtVtfq0ZwnlXr/hc4Y2wPY PrPYNWi1S5a7CtIRqK0XA== X-UI-Out-Filterresults: notjunk:1; Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tuesday 17 February 2015 13:05:50 Arun Ramamurthy wrote: > On 15-02-17 12:53 PM, Arnd Bergmann wrote: > > 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. > > > The patch was written in a way that all the existing and new drivers can > continue to use "usb" if they are using only one phy so that we remain > compatible. The names need to be different only if more than one phy is > specified. In such cases i don't think the first phy should be "usb" as > it would be confusing to have > phy-names = "usb","usbp1" I see your patch now, as 7e7a0e67f2c ("usb: ehci-platform: add support for multiple phys per controller"), and I'm not too happy about the way you did this. We already concluded that there should have been a binding change to go along with this, and that would have caught the fact that you circumvent the API here by reading the phy names manually. That part should never have made it into the kernel. I think we can do this either by defining specific names for the phy, or by changing the generic PHY binding to allow anonymous phy references (leaving out "phy-names" entirely), and adding a proper API for that. > Should I run this by Alan Stern? I've added him to Cc here. He clearly didn't know the background about the DT binding change, and should not need to, but he may have an opinion on what names we should use. > > 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? > > > Yes, we have three identical phys connected to a single host controller > and one of the phys is also connected to the device controller Ok, no problem with that, let's just make sure we come up with a good binding for it. Arnd From mboxrd@z Thu Jan 1 00:00:00 1970 From: arnd@arndb.de (Arnd Bergmann) Date: Wed, 18 Feb 2015 16:15:01 +0100 Subject: [PATCH 1/2] phy: usbphy: Add dt documentation for Broadcom Cygnus USB PHY driver In-Reply-To: <54E3AD2E.8050902@broadcom.com> References: <1424200821-16368-1-git-send-email-arun.ramamurthy@broadcom.com> <2797126.uqvyZJisPk@wuerfel> <54E3AD2E.8050902@broadcom.com> Message-ID: <11865413.8NsXkQ6AUR@wuerfel> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Tuesday 17 February 2015 13:05:50 Arun Ramamurthy wrote: > On 15-02-17 12:53 PM, Arnd Bergmann wrote: > > 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. > > > The patch was written in a way that all the existing and new drivers can > continue to use "usb" if they are using only one phy so that we remain > compatible. The names need to be different only if more than one phy is > specified. In such cases i don't think the first phy should be "usb" as > it would be confusing to have > phy-names = "usb","usbp1" I see your patch now, as 7e7a0e67f2c ("usb: ehci-platform: add support for multiple phys per controller"), and I'm not too happy about the way you did this. We already concluded that there should have been a binding change to go along with this, and that would have caught the fact that you circumvent the API here by reading the phy names manually. That part should never have made it into the kernel. I think we can do this either by defining specific names for the phy, or by changing the generic PHY binding to allow anonymous phy references (leaving out "phy-names" entirely), and adding a proper API for that. > Should I run this by Alan Stern? I've added him to Cc here. He clearly didn't know the background about the DT binding change, and should not need to, but he may have an opinion on what names we should use. > > 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? > > > Yes, we have three identical phys connected to a single host controller > and one of the phys is also connected to the device controller Ok, no problem with that, let's just make sure we come up with a good binding for it. Arnd