From: Bjorn Andersson <andersson@kernel.org>
To: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org,
Luca Weiss <luca.weiss@fairphone.com>
Subject: Re: [PATCH v2 0/4] clk: qcom: dispcc: fix DisplayPort link clocks
Date: Sat, 27 Apr 2024 14:34:16 -0500 [thread overview]
Message-ID: <171424646120.1448451.8800126789996663688.b4-ty@kernel.org> (raw)
In-Reply-To: <20240424-dispcc-dp-clocks-v2-0-b44038f3fa96@linaro.org>
On Wed, 24 Apr 2024 04:39:28 +0300, Dmitry Baryshkov wrote:
> On several Qualcomm platforms DisplayPort link clocks used incorrect
> frequency tables. Drop frequency tables and use clk_byte2_ops instead of
> clk_rcg2_ops.
>
> Note, this was tested on SM8450 only and then extended to other
> platforms.
>
> [...]
Applied, thanks!
[1/4] clk: qcom: dispcc-sm8450: fix DisplayPort clocks
commit: e801038a02ce1e8c652a0b668dd233a4ee48aeb7
[2/4] clk: qcom: dispcc-sm6350: fix DisplayPort clocks
commit: 1113501cfb46d5c0eb960f0a8a9f6c0f91dc6fb6
[3/4] clk: qcom: dispcc-sm8550: fix DisplayPort clocks
commit: e90b5139da8465a15c3820b4b67ca9468dce93b4
[4/4] clk: qcom: dispcc-sm8650: fix DisplayPort clocks
commit: 615a292ee4d51303246278f3fa33cc38700fe00e
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2024-04-27 19:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 1:39 [PATCH v2 0/4] clk: qcom: dispcc: fix DisplayPort link clocks Dmitry Baryshkov
2024-04-24 1:39 ` [PATCH v2 1/4] clk: qcom: dispcc-sm8450: fix DisplayPort clocks Dmitry Baryshkov
2024-04-24 1:39 ` [PATCH v2 2/4] clk: qcom: dispcc-sm6350: " Dmitry Baryshkov
2024-04-24 1:39 ` [PATCH v2 3/4] clk: qcom: dispcc-sm8550: " Dmitry Baryshkov
2024-04-24 1:39 ` [PATCH v2 4/4] clk: qcom: dispcc-sm8650: " Dmitry Baryshkov
2024-04-27 19:34 ` Bjorn Andersson [this message]
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=171424646120.1448451.8800126789996663688.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=konrad.dybcio@linaro.org \
--cc=konrad.dybcio@somainline.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.weiss@fairphone.com \
--cc=mturquette@baylibre.com \
--cc=neil.armstrong@linaro.org \
--cc=sboyd@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 read-only IMAP folder(s) and NNTP newsgroup(s).