From: Stephen Boyd <sboyd@codeaurora.org>
To: Vivek Gautam <vivek.gautam@codeaurora.org>
Cc: kishon <kishon@ti.com>, robh+dt <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v2 3/4] dt-bindings: phy: Add support for QMP phy
Date: Wed, 30 Nov 2016 11:12:07 -0800 [thread overview]
Message-ID: <20161130191207.GJ6095@codeaurora.org> (raw)
In-Reply-To: <CAFp+6iGeNQKuP=WmshPG0088CNy8hosdfN+unuS6bhYqJJaKRQ@mail.gmail.com>
On 11/29, Vivek Gautam wrote:
> On Tue, Nov 29, 2016 at 4:25 AM, Stephen Boyd <sboyd@codeaurora.org> wrote:
> > On 11/22, Vivek Gautam wrote:
> >> diff --git a/Documentation/devicetree/bindings/phy/qcom-qmp-phy.txt b/Documentation/devicetree/bindings/phy/qcom-qmp-phy.txt
> >> new file mode 100644
> >> index 0000000..ffb173b
> >> --- /dev/null
> >> +++ b/Documentation/devicetree/bindings/phy/qcom-qmp-phy.txt
> >> @@ -0,0 +1,74 @@
>
> >
> >> + "pipe<port-number>" for pipe clock specific to
> >> + each port/lane (Optional).
> >
> > The pipe clocks are orphaned right now. We should add an output
> > clock from the phy to go into the controller and back into the
> > phy if I recall correctly. The phy should be a clock provider
> > itself so it can output the pipe clock source into GCC and back
> > into the phy and controller.
> >
> >> + - resets: a list of phandles and reset controller specifier pairs,
> >> + one for each entry in reset-names.
> >> + - reset-names: must be "phy" for reset of phy block,
> >> + "common" for phy common block reset,
> >> + "cfg" for phy's ahb cfg block reset (Optional).
> >> + "port<port-number>" for reset specific to
> >> + each port/lane (Optional).
> >> + - vdda-phy-supply: Phandle to a regulator supply to PHY core block.
> >> + - vdda-pll-supply: Phandle to 1.8V regulator supply to PHY refclk pll block.
> >> +
> >> +Optional properties:
> >> + - vddp-ref-clk-supply: Phandle to a regulator supply to any specific refclk
> >> + pll block.
> >> +
> >> +Example:
> >> + pcie_phy: pciephy@34000 {
> >
> > pcie-phy or just phy as the node name?
>
> How about just 'phy'? The label pcie_phy anyways explains the use.
>
>
phy is a great color choice for the shed.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2016-11-30 19:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 12:02 [PATCH v2 0/4] phy: USB and PCIe phy drivers for Qcom chipsets Vivek Gautam
2016-11-22 12:02 ` [PATCH v2 1/4] dt-bindings: phy: Add support for QUSB2 phy Vivek Gautam
2016-11-28 14:19 ` Rob Herring
2016-11-29 5:20 ` Vivek Gautam
[not found] ` <1479816163-5260-2-git-send-email-vivek.gautam-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2016-11-28 22:49 ` Stephen Boyd
2016-11-29 5:22 ` Vivek Gautam
2016-11-22 12:02 ` [PATCH v2 2/4] phy: qcom-qusb2: New driver for QUSB2 PHY on Qcom chips Vivek Gautam
[not found] ` <1479816163-5260-3-git-send-email-vivek.gautam-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2016-11-28 23:14 ` Stephen Boyd
[not found] ` <20161128231424.GN6095-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2016-12-01 8:42 ` Vivek Gautam
2016-12-02 18:47 ` Stephen Boyd
2016-12-06 8:11 ` Vivek Gautam
2016-11-22 12:02 ` [PATCH v2 3/4] dt-bindings: phy: Add support for QMP phy Vivek Gautam
[not found] ` <1479816163-5260-4-git-send-email-vivek.gautam-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2016-11-28 22:55 ` Stephen Boyd
2016-11-29 5:25 ` Vivek Gautam
2016-11-30 19:12 ` Stephen Boyd [this message]
[not found] ` <20161128225543.GM6095-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2016-12-12 16:40 ` Vivek Gautam
2016-11-28 23:19 ` Stephen Boyd
2016-12-13 9:18 ` Vivek Gautam
2016-11-22 12:02 ` [PATCH v2 4/4] phy: qcom-qmp: new qmp phy driver for qcom-chipsets Vivek Gautam
2016-11-29 0:35 ` Stephen Boyd
2016-12-20 5:42 ` Vivek Gautam
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=20161130191207.GJ6095@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=vivek.gautam@codeaurora.org \
/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).