From: Stephen Boyd <sboyd@kernel.org>
To: Bjorn Andersson <andersson@kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Michael Turquette <mturquette@baylibre.com>,
Neil Armstrong <neil.armstrong@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] clk: qcom: dispcc-sm8450: fix DisplayPort clocks
Date: Mon, 08 Apr 2024 19:34:52 -0700 [thread overview]
Message-ID: <ad3e3201fbea1f73f1550877d5c12ba5.sboyd@kernel.org> (raw)
In-Reply-To: <20240408-dispcc-dp-clocks-v1-1-f9e44902c28d@linaro.org>
Quoting Dmitry Baryshkov (2024-04-08 04:47:04)
> On SM8450 DisplayPort link clocks use frequency tables inherited from
> the vendor kernel, it is not applicable in the upstream kernel. Drop
> frequency tables and use clk_byte2_ops for those clocks.
The subject says "fix", but does this fix anything, or simply optimize?
Is something broken by having the frequency table?
next prev parent reply other threads:[~2024-04-09 2:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 11:47 [PATCH 0/4] clk: qcom: dispcc: fix DisplayPort link clocks Dmitry Baryshkov
2024-04-08 11:47 ` [PATCH 1/4] clk: qcom: dispcc-sm8450: fix DisplayPort clocks Dmitry Baryshkov
2024-04-09 2:34 ` Stephen Boyd [this message]
2024-04-10 16:27 ` Neil Armstrong
2024-04-10 17:11 ` Dmitry Baryshkov
2024-04-08 11:47 ` [PATCH 2/4] clk: qcom: dispcc-sm6350: " Dmitry Baryshkov
2024-04-10 16:32 ` Neil Armstrong
2024-04-11 11:33 ` Luca Weiss
2024-04-08 11:47 ` [PATCH 3/4] clk: qcom: dispcc-sm8550: " Dmitry Baryshkov
2024-04-10 16:26 ` Neil Armstrong
2024-04-08 11:47 ` [PATCH 4/4] clk: qcom: dispcc-sm8650: " Dmitry Baryshkov
2024-04-10 16:31 ` Neil Armstrong
2024-04-10 18:46 ` [PATCH 0/4] clk: qcom: dispcc: fix DisplayPort link clocks Konrad Dybcio
2024-04-20 18:05 ` 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=ad3e3201fbea1f73f1550877d5c12ba5.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=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=mturquette@baylibre.com \
--cc=neil.armstrong@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