From: Rob Herring <robh@kernel.org>
To: Bhupesh Sharma <bhupesh.sharma@linaro.org>
Cc: lorenzo.pieralisi@arm.com, bjorn.andersson@linaro.org,
linux-pci@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-msm@vger.kernel.org, bhupesh.linux@gmail.com,
bhelgaas@google.com, linux-kernel@vger.kernel.org,
robh+dt@kernel.org, agross@kernel.org, svarbanov@mm-sol.com
Subject: Re: [PATCH 2/6] dt-bindings: phy: qcom,qmp: Add SM8150 PCIe PHY bindings
Date: Fri, 25 Feb 2022 13:44:03 -0600 [thread overview]
Message-ID: <Yhkxg1wjduMX22Mo@robh.at.kernel.org> (raw)
In-Reply-To: <20220223192946.473172-3-bhupesh.sharma@linaro.org>
On Thu, 24 Feb 2022 00:59:42 +0530, Bhupesh Sharma wrote:
> Add the following two PCIe PHYs found on SM8150, to the QMP binding:
>
> QMP GEN3x1 PHY - 1 lane
> QMP GEN3x2 PHY - 2 lanes
>
> Cc: Rob Herring <robh@kernel.org>
> Signed-off-by: Bhupesh Sharma <bhupesh.sharma@linaro.org>
> ---
> Documentation/devicetree/bindings/phy/qcom,qmp-phy.yaml | 4 ++++
> 1 file changed, 4 insertions(+)
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-02-25 19:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 19:29 [PATCH 0/6] Add PCIe support for SM8150 SoC Bhupesh Sharma
2022-02-23 19:29 ` [PATCH 1/6] dt-bindings: pci: qcom: Document PCIe bindings " Bhupesh Sharma
2022-02-25 19:43 ` Rob Herring
2022-02-23 19:29 ` [PATCH 2/6] dt-bindings: phy: qcom,qmp: Add SM8150 PCIe PHY bindings Bhupesh Sharma
2022-02-23 20:36 ` Rob Herring
2022-02-24 11:12 ` Bhupesh Sharma
2022-02-25 19:44 ` Rob Herring [this message]
2022-02-23 19:29 ` [PATCH 3/6] phy: qcom-qmp: Add SM8150 PCIe QMP PHYs Bhupesh Sharma
2022-02-23 19:29 ` [PATCH 4/6] PCI: qcom: Add SM8150 SoC support Bhupesh Sharma
2022-02-23 21:51 ` Dmitry Baryshkov
2022-02-23 19:29 ` [PATCH 5/6] arm64: dts: qcom: sm8150: Add pcie nodes for SM8150 Bhupesh Sharma
2022-02-23 19:29 ` [PATCH 6/6] arm64: dts: qcom: sa8155: Enable pcie nodes Bhupesh Sharma
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=Yhkxg1wjduMX22Mo@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=agross@kernel.org \
--cc=bhelgaas@google.com \
--cc=bhupesh.linux@gmail.com \
--cc=bhupesh.sharma@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=robh+dt@kernel.org \
--cc=svarbanov@mm-sol.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).