From: Shawn Guo <shawn.guo@linaro.org>
To: Kishon Vijay Abraham I <kishon@ti.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Jianguo Sun <sunjianguo1@huawei.com>,
Jiancheng Xue <xuejiancheng@hisilicon.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Pengcheng Li <lpc.li@hisilicon.com>
Subject: Re: [PATCH v3 1/2] dt-bindings: add bindings doc for HiSilicon INNO USB2 PHY
Date: Fri, 2 Mar 2018 16:45:18 +0800 [thread overview]
Message-ID: <20180302084516.GD28619@dragon> (raw)
In-Reply-To: <05d00dd2-efe2-1166-d982-06df0e3b8611@ti.com>
On Fri, Mar 02, 2018 at 01:35:43PM +0530, Kishon Vijay Abraham I wrote:
> >>> diff --git a/Documentation/devicetree/bindings/phy/phy-hisi-inno-usb2.txt b/Documentation/devicetree/bindings/phy/phy-hisi-inno-usb2.txt
> >>> new file mode 100644
> >>> index 000000000000..b563cf54ca7b
> >>> --- /dev/null
> >>> +++ b/Documentation/devicetree/bindings/phy/phy-hisi-inno-usb2.txt
> >>> @@ -0,0 +1,52 @@
> >>> +HiSilicon INNO USB2 PHY
> >>> +
> >>> +Required properties:
> >>> +- compatible: Should be one of the following strings:
> >>> + "hisilicon,inno-usb2-phy",
> >>> + "hisilicon,hi3798cv200-usb2-phy".
> >>> +- reg: Should be the address space for PHY configuration register in peripheral
> >>> + controller, e.g. PERI_USB0 for USB 2.0 PHY01 on Hi3798cv200 SoC.
> >>> +- #phy-cells: Should be 1. The specifier is the index of the PHY port to
> >>> + reference.
> >>
> >> This can be '0' if the consumers directly use phandle to the subnodes.
> >
> > Yes, I understand that for most of PHY devices #phy-cells is just 0, and
> > consumers simply use the phandle without any cell number. But for this
> > inno-usb2-phy, every single device contains two PHY ports, and each port
>
> Why not have a separate sub-node for each phy port? Then you can just use
> phandle to the subnode in the controller node.
It sounds like a sensible suggestion. I will try to implement that and
see how it goes. Thanks.
Shawn
next prev parent reply other threads:[~2018-03-02 8:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 7:22 [PATCH v3 0/2] Add HiSilicon INNO USB2 PHY driver support Shawn Guo
2018-03-01 7:22 ` [PATCH v3 1/2] dt-bindings: add bindings doc for HiSilicon INNO USB2 PHY Shawn Guo
2018-03-02 6:25 ` Kishon Vijay Abraham I
2018-03-02 7:37 ` Shawn Guo
2018-03-02 8:05 ` Kishon Vijay Abraham I
2018-03-02 8:45 ` Shawn Guo [this message]
2018-03-01 7:22 ` [PATCH v3 2/2] phy: add inno-usb2-phy driver for hi3798cv200 SoC Shawn Guo
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=20180302084516.GD28619@dragon \
--to=shawn.guo@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lpc.li@hisilicon.com \
--cc=robh+dt@kernel.org \
--cc=sunjianguo1@huawei.com \
--cc=xuejiancheng@hisilicon.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).