Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753820AbbBZAW2 (ORCPT ); Wed, 25 Feb 2015 19:22:28 -0500 Received: from mail-gw1-out.broadcom.com ([216.31.210.62]:57217 "EHLO mail-gw1-out.broadcom.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753189AbbBZAW0 (ORCPT ); Wed, 25 Feb 2015 19:22:26 -0500 X-IronPort-AV: E=Sophos;i="5.09,648,1418112000"; d="scan'208";a="58203249" Message-ID: <54EE67A6.609@broadcom.com> Date: Wed, 25 Feb 2015 16:24:06 -0800 From: Arun Ramamurthy User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Arnd Bergmann , , Alan Stern CC: Mark Rutland , , "Scott Branden" , Pawel Moll , "Ian Campbell" , Ray Jui , , Kishon Vijay Abraham I , Jonathan Richardson , Rob Herring , , "Dmitry Torokhov" , Kumar Gala , "Anatol Pomazau" Subject: Re: [PATCH 1/2] phy: usbphy: Add dt documentation for Broadcom Cygnus USB PHY driver References: <1424200821-16368-1-git-send-email-arun.ramamurthy@broadcom.com> <2797126.uqvyZJisPk@wuerfel> <54E3AD2E.8050902@broadcom.com> <11865413.8NsXkQ6AUR@wuerfel> <54E53278.70705@broadcom.com> In-Reply-To: <54E53278.70705@broadcom.com> Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3394 Lines: 80 Hello Alan and Arnd I wanted to follow up on this patch and ascertain what I would have to change. Please see below for my questions On 15-02-18 04:46 PM, Arun Ramamurthy wrote: > > > On 15-02-18 07:15 AM, Arnd Bergmann wrote: >> 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. >> > Thanks Arnd, I will wait for Alan's comments before proceeding. I am > happy to patch the ehci-platform driver to use a new api instead of > devm_phy_get if that is the best option. > >>> 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. >> > Arnd, should I re patch the ehci-platform driver to avoid phy-names entirely? Alan, if not do you have an opinion on what the usb phy names should be? The current patch uses "usbp" + port number such as "usbp0" , "usbp1" etc >>>> 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 do you have any other comments on the phy driver itself? Thank you >> 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/