From: Rob Herring <robh@kernel.org>
To: Shawn Guo <shawn.guo@linaro.org>
Cc: Jami Kettunen <jamipkettunen@gmail.com>,
Jeffrey Hugo <jeffrey.l.hugo@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@somainline.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
Konrad Dybcio <konrad.dybcio@somainline.org>,
linux-phy@lists.infradead.org,
Bjorn Andersson <bjorn.andersson@linaro.org>,
linux-kernel@vger.kernel.org, Vinod Koul <vkoul@kernel.org>
Subject: Re: [PATCH v2 1/3] dt-bindings: phy: qcom,qusb2: Add missing vdd-supply
Date: Mon, 4 Oct 2021 13:24:17 -0500 [thread overview]
Message-ID: <YVtG0Ykkfy3/Am3J@robh.at.kernel.org> (raw)
In-Reply-To: <20210928022002.26286-2-shawn.guo@linaro.org>
On Tue, 28 Sep 2021 10:20:00 +0800, Shawn Guo wrote:
> Besides vdda-pll and vdda-phy-dpdm, vdd-supply is a required supply for
> PHY digital circuit operation. Add it for correctness and completeness.
>
> Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
> ---
> Documentation/devicetree/bindings/phy/qcom,qusb2-phy.yaml | 6 ++++++
> 1 file changed, 6 insertions(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2021-10-04 18:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 2:19 [PATCH v2 0/3] Add missing vdd-supply for QUSB2 PHY Shawn Guo
2021-09-28 2:20 ` [PATCH v2 1/3] dt-bindings: phy: qcom,qusb2: Add missing vdd-supply Shawn Guo
2021-10-04 18:24 ` Rob Herring [this message]
2021-09-28 2:20 ` [PATCH v2 2/3] phy: qcom-qusb2: Add missing vdd supply Shawn Guo
2021-09-28 2:20 ` [PATCH v2 3/3] arm64: dts: qcom: Add missing vdd-supply for QUSB2 PHY Shawn Guo
2021-10-05 7:49 ` Vinod Koul
2021-11-20 23:55 ` (subset) " Bjorn Andersson
2021-10-01 8:16 ` [PATCH v2 0/3] " Vinod Koul
2021-10-04 3:01 ` Shawn Guo
2021-10-05 7:47 ` Vinod Koul
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=YVtG0Ykkfy3/Am3J@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=angelogioacchino.delregno@somainline.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=jamipkettunen@gmail.com \
--cc=jeffrey.l.hugo@gmail.com \
--cc=konrad.dybcio@somainline.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=shawn.guo@linaro.org \
--cc=vkoul@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 NNTP newsgroup(s).