From: Taniya Das <taniya.das@oss.qualcomm.com>
To: Pengyu Luo <mitltlatltl@gmail.com>,
Bjorn Andersson <andersson@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: qcom: rcg2: expand frac table for mdss_pixel_clk_src
Date: Mon, 23 Mar 2026 09:54:49 +0530 [thread overview]
Message-ID: <100b51e4-b6d5-4d17-8721-b2ea1ee747e0@oss.qualcomm.com> (raw)
In-Reply-To: <20260321095029.2259489-1-mitltlatltl@gmail.com>
On 3/21/2026 3:20 PM, Pengyu Luo wrote:
> Downstream clk_summary shows the mdss_pixel_clk_src support the
> ratio(35:16)
>
> dsi0_phy_pll_out_dsiclk 2 2 0 378420000
> disp_cc_mdss_pclk1_clk_src 1 1 0 172992000
> dsi0_phy_pll_out_byteclk 2 2 0 108120000
> disp_cc_mdss_byte1_clk_src 2 2 0 108120000
>
> After checking downstream source, 15:4 also seems to be supported,
> add them two.
>
> Signed-off-by: Pengyu Luo <mitltlatltl@gmail.com>
> ---
> drivers/clk/qcom/clk-rcg2.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/clk/qcom/clk-rcg2.c b/drivers/clk/qcom/clk-rcg2.c
> index fc696b66cc..6064a0e17d 100644
> --- a/drivers/clk/qcom/clk-rcg2.c
> +++ b/drivers/clk/qcom/clk-rcg2.c
> @@ -1117,6 +1117,8 @@ static const struct frac_entry frac_table_pixel[] = {
> { 4, 9 },
> { 1, 1 },
> { 2, 3 },
> + { 16, 35},
> + { 4, 15},
> { }
> };
>
Reviewed-by: Taniya Das <taniya.das@oss.qualcomm.com>
--
Thanks,
Taniya Das
next prev parent reply other threads:[~2026-03-23 4:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-21 9:50 [PATCH] clk: qcom: rcg2: expand frac table for mdss_pixel_clk_src Pengyu Luo
2026-03-21 21:46 ` Dmitry Baryshkov
2026-03-23 4:24 ` Taniya Das [this message]
2026-03-23 4:26 ` Taniya Das
2026-03-23 12:54 ` Konrad Dybcio
2026-03-23 19:23 ` Dmitry Baryshkov
2026-03-24 9:22 ` Konrad Dybcio
2026-03-24 12:56 ` Pengyu Luo
2026-03-24 13:00 ` Konrad Dybcio
2026-03-24 3: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=100b51e4-b6d5-4d17-8721-b2ea1ee747e0@oss.qualcomm.com \
--to=taniya.das@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mitltlatltl@gmail.com \
--cc=mturquette@baylibre.com \
--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