From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Johan Hovold <johan+linaro@kernel.org>,
Vinod Koul <vkoul@kernel.org>,
Bjorn Andersson <andersson@kernel.org>
Cc: Andy Gross <agross@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@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 3/3] arm64: dts: qcom: sc8280xp: drop reference-clock source
Date: Sat, 12 Nov 2022 14:49:40 +0300 [thread overview]
Message-ID: <4c3dd58e-7162-3457-c785-dbd44eab7628@linaro.org> (raw)
In-Reply-To: <20221111093857.11360-4-johan+linaro@kernel.org>
On 11/11/2022 12:38, Johan Hovold wrote:
> The source clock for the reference clock should not be described by the
> devicetree binding and instead this relationship should be modelled in
> the clock driver.
>
> Update the USB PHY nodes to match the fixed binding.
>
> Signed-off-by: Johan Hovold <johan+linaro@kernel.org>
> ---
> arch/arm64/boot/dts/qcom/sc8280xp.dtsi | 8 ++------
> 1 file changed, 2 insertions(+), 6 deletions(-)
Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
--
With best wishes
Dmitry
next prev parent reply other threads:[~2022-11-12 11:49 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
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 [this message]
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=4c3dd58e-7162-3457-c785-dbd44eab7628@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.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).