From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Neil Armstrong <neil.armstrong@linaro.org>
Subject: Re: [PATCH 2/2] arm64: dts: qcom: sm8550: correct TX Soundwire clock
Date: Wed, 29 Nov 2023 15:35:15 +0100 [thread overview]
Message-ID: <3ec70fd9-11a3-4bd3-bd8c-a73c3d44dcde@linaro.org> (raw)
In-Reply-To: <20231129140537.161720-2-krzysztof.kozlowski@linaro.org>
On 29.11.2023 15:05, Krzysztof Kozlowski wrote:
> The TX Soundwire controller should take clock from TX macro codec, not
> VA macro codec clock, otherwise the clock stays disabled. This looks
> like a copy-paste issue, because the SC8280xp code uses here correctly
> clock from TX macro. The VA macro clock is already consumed by TX macro
> codec, thus it won't be disabled by this change.
>
> Fixes: 61b006389bb7 ("arm64: dts: qcom: sm8550: add Soundwire controllers")
> Reported-by: Neil Armstrong <neil.armstrong@linaro.org>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> ---
Interestingly, downstream 8550 has
qcom,use-clk-id = <VA_CORE_CLK>;
which doesn't seem to be used in techpack
Konrad
next prev parent reply other threads:[~2023-11-29 14:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 14:05 [PATCH 1/2] arm64: dts: qcom: sm8450: correct TX Soundwire clock Krzysztof Kozlowski
2023-11-29 14:05 ` [PATCH 2/2] arm64: dts: qcom: sm8550: " Krzysztof Kozlowski
2023-11-29 14:35 ` Konrad Dybcio [this message]
2023-11-30 8:06 ` Krzysztof Kozlowski
2023-11-30 9:17 ` Neil Armstrong
2023-11-30 10:11 ` Konrad Dybcio
2023-11-30 9:52 ` Neil Armstrong
2023-11-29 14:26 ` [PATCH 1/2] arm64: dts: qcom: sm8450: " Konrad Dybcio
2023-11-30 9:52 ` Neil Armstrong
2023-12-03 4:54 ` (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=3ec70fd9-11a3-4bd3-bd8c-a73c3d44dcde@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.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).