From: Bjorn Andersson <andersson@kernel.org>
To: Johan Hovold <johan+linaro@kernel.org>
Cc: Vinod Koul <vkoul@kernel.org>, Andy Gross <agross@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: phy: qcom,sc8280xp-qmp-usb3-uni: drop reference-clock source
Date: Fri, 11 Nov 2022 14:26:57 -0600 [thread overview]
Message-ID: <20221111202657.kyzay7oy4yojp4xo@builder.lan> (raw)
In-Reply-To: <20221111093857.11360-2-johan+linaro@kernel.org>
On Fri, Nov 11, 2022 at 10:38:55AM +0100, Johan Hovold wrote:
> The source clock for the reference clock is not used by the PHY directly
> and should not be included in the devicetree binding.
>
> Fixes: e8e58e29a0c9 ("dt-bindings: phy: qcom,qmp-usb: fix sc8280xp binding")
> Signed-off-by: Johan Hovold <johan+linaro@kernel.org>
Reviewed-by: Bjorn Andersson <andersson@kernel.org>
> ---
> .../bindings/phy/qcom,sc8280xp-qmp-usb3-uni-phy.yaml | 7 ++-----
> 1 file changed, 2 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/phy/qcom,sc8280xp-qmp-usb3-uni-phy.yaml b/Documentation/devicetree/bindings/phy/qcom,sc8280xp-qmp-usb3-uni-phy.yaml
> index ef080509747a..16fce1038285 100644
> --- a/Documentation/devicetree/bindings/phy/qcom,sc8280xp-qmp-usb3-uni-phy.yaml
> +++ b/Documentation/devicetree/bindings/phy/qcom,sc8280xp-qmp-usb3-uni-phy.yaml
> @@ -22,12 +22,11 @@ properties:
> maxItems: 1
>
> clocks:
> - maxItems: 5
> + maxItems: 4
>
> clock-names:
> items:
> - const: aux
> - - const: ref_clk_src
> - const: ref
> - const: com_aux
> - const: pipe
> @@ -82,12 +81,10 @@ examples:
> reg = <0x088ef000 0x2000>;
>
> clocks = <&gcc GCC_USB3_MP_PHY_AUX_CLK>,
> - <&rpmhcc RPMH_CXO_CLK>,
> <&gcc GCC_USB3_MP0_CLKREF_CLK>,
> <&gcc GCC_USB3_MP_PHY_COM_AUX_CLK>,
> <&gcc GCC_USB3_MP_PHY_PIPE_0_CLK>;
> - clock-names = "aux", "ref_clk_src", "ref", "com_aux",
> - "pipe";
> + clock-names = "aux", "ref", "com_aux", "pipe";
>
> power-domains = <&gcc USB30_MP_GDSC>;
>
> --
> 2.37.4
>
next prev parent reply other threads:[~2022-11-11 20:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 9:38 [PATCH 0/3] phy: qcom-qmp-usb: drop sc8280xp reference-clock source Johan Hovold
2022-11-11 9:38 ` [PATCH 1/3] dt-bindings: phy: qcom,sc8280xp-qmp-usb3-uni: drop " Johan Hovold
2022-11-11 20:26 ` Bjorn Andersson [this message]
2022-11-15 13:38 ` Krzysztof Kozlowski
2022-11-11 9:38 ` [PATCH 2/3] phy: qcom-qmp-usb: drop sc8280xp " Johan Hovold
2022-11-11 20:27 ` Bjorn Andersson
2022-11-12 11:49 ` Dmitry Baryshkov
2022-11-11 9:38 ` [PATCH 3/3] arm64: dts: qcom: sc8280xp: drop " Johan Hovold
2022-11-12 11:49 ` Dmitry Baryshkov
2022-11-24 17:24 ` [PATCH 0/3] phy: qcom-qmp-usb: drop sc8280xp " Vinod Koul
2022-12-06 18:18 ` (subset) " Bjorn Andersson
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=20221111202657.kyzay7oy4yojp4xo@builder.lan \
--to=andersson@kernel.org \
--cc=agross@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=johan+linaro@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=robh+dt@kernel.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).