From: Kishon Vijay Abraham I <kishon@ti.com>
To: Doug Anderson <dianders@chromium.org>
Cc: "Tao Huang" <huangtao@rock-chips.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"Heiko Stübner" <heiko@sntech.de>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Chris <zyw@rock-chips.com>, "Eddie Cai" <cf@rock-chips.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Yunzhi Li" <lyz@rock-chips.com>,
"Olof Johansson" <olof@lixom.net>,
jwerner@chromium.org,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Grant Likely" <grant.likely@linaro.org>
Subject: Re: [PATCH v6 1/5] phy: add a driver for the Rockchip SoC internal USB2.0 PHY
Date: Fri, 12 Dec 2014 11:17:01 +0530 [thread overview]
Message-ID: <548A8155.8080809@ti.com> (raw)
In-Reply-To: <CAD=FV=XTYmzxvteNip2gtuDSSEWph-vY=BOPejHa1Z5KS2Kf6Q@mail.gmail.com>
Hi,
On Friday 12 December 2014 12:11 AM, Doug Anderson wrote:
> Kishon,
>
> On Thu, Dec 11, 2014 at 2:27 AM, Kishon Vijay Abraham I <kishon@ti.com> wrote:
>> I didn't mean that. You can get rid of this entire xlate stuff if you use
>> something like below
>>
>> phy@xxx {
>> compatible = "";
>> phy1:usb_phy {
>> }
>> phy2:usb_phy {
>> };
>> };
>>
>>
>> usb@xx {
>> compatible = "";
>> phys = <&phy1>; //doesn't need xlate
>> /* this needs xlate
>> phys = <&phy 1>;
>> */
>> phy-names = "phy";
>> };
>
> Is the syntax you proposed really better? Are you saying that you
> advocate never using "#phy-cells" other than 0 for new bindings? Is
No. It can still be used for configuring the PHY. For example, in the case of
PIPE3 PHY we configure it to USB PHY, SATA PHY or PCIE PHY depending on to
which controller the PHY is connected to.
I feel using phy-cells just for differentiating the PHY is pointless when you
have a separate node for each PHY.
Thanks
Kishon
next prev parent reply other threads:[~2014-12-12 5:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 9:55 [PATCH v6 0/5] Patches to add support for Rockchip usb PHYs Yunzhi Li
2014-12-11 9:55 ` [PATCH v6 1/5] phy: add a driver for the Rockchip SoC internal USB2.0 PHY Yunzhi Li
2014-12-11 10:27 ` Kishon Vijay Abraham I
[not found] ` <548971AF.1020506-l0cyMroinI0@public.gmane.org>
2014-12-11 13:45 ` Yunzhi Li
2014-12-12 5:34 ` Kishon Vijay Abraham I
2014-12-11 18:41 ` Doug Anderson
2014-12-12 5:47 ` Kishon Vijay Abraham I [this message]
2014-12-12 5:51 ` Doug Anderson
2014-12-11 18:09 ` Doug Anderson
2014-12-12 3:05 ` Doug Anderson
2014-12-12 3:43 ` Yunzhi Li
2014-12-11 9:55 ` [PATCH v6 2/5] Documentation: bindings: add dt documentation for Rockchip usb PHY Yunzhi Li
[not found] ` <1418291722-25448-3-git-send-email-lyz-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2014-12-11 18:46 ` Doug Anderson
2014-12-11 18:49 ` Doug Anderson
2014-12-11 9:55 ` [PATCH v6 4/5] ARM: dts: rockchip: add rk3288 " Yunzhi Li
2014-12-11 10:11 ` [PATCH v6 5/5] ARM: dts: rockchip: Enable usb PHY on rk3288-evb board Yunzhi Li
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=548A8155.8080809@ti.com \
--to=kishon@ti.com \
--cc=cf@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=grant.likely@linaro.org \
--cc=heiko@sntech.de \
--cc=huangtao@rock-chips.com \
--cc=jwerner@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=lyz@rock-chips.com \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=zyw@rock-chips.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).