From: Stephen Boyd <swboyd@chromium.org>
To: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Prasad Malisetty <pmaliset@codeaurora.org>,
Rob Herring <robh+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
mgautam@codeaurora.org, dianders@chromium.org, mka@chromium.org
Subject: Re: [PATCH 1/3] dt-bindings: pci: qcom: Document PCIe bindings for SC720
Date: Fri, 7 May 2021 12:59:00 -0700 [thread overview]
Message-ID: <CAE-0n53KTeF9NOrb+x7P1AG53FENRBGtCEcSxronBpJoww3jew@mail.gmail.com> (raw)
In-Reply-To: <1620382648-17395-2-git-send-email-pmaliset@codeaurora.org>
Quoting Prasad Malisetty (2021-05-07 03:17:26)
> Document the PCIe DT bindings for SC7280 SoC.The PCIe IP is similar
> to the one used on SM8250. Add the compatible for SC7280.
>
> Signed-off-by: Prasad Malisetty <pmaliset@codeaurora.org>
> ---
> Documentation/devicetree/bindings/pci/qcom,pcie.txt | 17 +++++++++++++++++
> 1 file changed, 17 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/pci/qcom,pcie.txt b/Documentation/devicetree/bindings/pci/qcom,pcie.txt
> index 0da458a..e5245ed 100644
> --- a/Documentation/devicetree/bindings/pci/qcom,pcie.txt
> +++ b/Documentation/devicetree/bindings/pci/qcom,pcie.txt
> @@ -12,6 +12,7 @@
> - "qcom,pcie-ipq4019" for ipq4019
> - "qcom,pcie-ipq8074" for ipq8074
> - "qcom,pcie-qcs404" for qcs404
> + - "qcom,pcie-sc7280" for sc7280
> - "qcom,pcie-sdm845" for sdm845
> - "qcom,pcie-sm8250" for sm8250
>
> @@ -133,6 +134,22 @@
> - "slave_bus" AXI Slave clock
>
> - clock-names:
> + Usage: required for sc7280
> + Value type: <stringlist>
> + Definition: Should contain the following entries
> + - "aux" Auxiliary clock
> + - "cfg" Configuration clock
> + - "bus_master" Master AXI clock
> + - "bus_slave" Slave AXI clock
> + - "slave_q2a" Slave Q2A clock
> + - "tbu" PCIe TBU clock
> + - "ddrss_sf_tbu" PCIe SF TBU clock
> + - "pipe" PIPE clock
> + - "pipe_src" PIPE MUX
Is pipe_src necessary? Is it the parent of the pipe clk? If so, please
remove it and do whatever is necessary on the pipe clk instead of the
parent of the clk.
> + - "pipe_ext" PIPE output clock
Is pipe output different from pipe?
> + - "ref" REFERENCE clock
> +
>
next prev parent reply other threads:[~2021-05-07 19:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-07 10:17 [PATCH 0/3] Add DT bindings and DT nodes for PCIe and PHY in SC7280 Prasad Malisetty
2021-05-07 10:17 ` [PATCH 1/3] dt-bindings: pci: qcom: Document PCIe bindings for SC720 Prasad Malisetty
2021-05-07 19:59 ` Stephen Boyd [this message]
2021-06-04 11:26 ` Prasad Malisetty
2021-06-04 21:44 ` Stephen Boyd
2021-05-10 15:48 ` Rob Herring
2021-05-07 10:17 ` [PATCH 2/3] arm64: dts: qcom: sc7280: Add PCIe and PHY related nodes Prasad Malisetty
2021-05-07 20:06 ` Stephen Boyd
2021-05-21 9:57 ` Prasad Malisetty
2021-06-04 21:43 ` Stephen Boyd
2021-06-06 4:02 ` Bjorn Andersson
2021-06-15 5:26 ` Prasad Malisetty
2021-05-07 10:17 ` [PATCH 3/3] arm64: dts: qcom: sc7280: Add PCIe nodes for IDP board Prasad Malisetty
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=CAE-0n53KTeF9NOrb+x7P1AG53FENRBGtCEcSxronBpJoww3jew@mail.gmail.com \
--to=swboyd@chromium.org \
--cc=agross@kernel.org \
--cc=bhelgaas@google.com \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mgautam@codeaurora.org \
--cc=mka@chromium.org \
--cc=pmaliset@codeaurora.org \
--cc=robh+dt@kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).