From: Alexandre Mergnat <amergnat@baylibre.com>
To: AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
sboyd@kernel.org
Cc: mturquette@baylibre.com, matthias.bgg@gmail.com,
wenst@chromium.org, msp@baylibre.com, yangyingliang@huawei.com,
u.kleine-koenig@pengutronix.de, miles.chen@mediatek.com,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, kernel@collabora.com
Subject: Re: [PATCH 2/2] clk: mediatek: mt8195-topckgen: Refactor parents for top_dp/edp muxes
Date: Thu, 13 Jul 2023 15:22:41 +0200 [thread overview]
Message-ID: <9a0817c2-4101-5c21-977d-77ac0d83a067@baylibre.com> (raw)
In-Reply-To: <20230713072138.84117-3-angelogioacchino.delregno@collabora.com>
On 13/07/2023 09:21, AngeloGioacchino Del Regno wrote:
> The top_dp and top_edp muxes can be both parented to either TVDPLL1
> or TVDPLL2, two identically specced PLLs for the specific purpose of
> giving out pixel clock: this becomes a problem when the MediaTek
> DisplayPort Interface (DPI) driver tries to set the pixel clock rate.
>
> In the usecase of two simultaneous outputs (using two controllers),
> it was seen that one of the displays would sometimes display garbled
> output (if any at all) and this was because:
> - top_edp was set to TVDPLL1, outputting X GHz
> - top_dp was set to TVDPLL2, outputting Y GHz
> - mtk_dpi calls clk_set_rate(top_edp, Z GHz)
> - top_dp is switched to TVDPLL1
> - TVDPLL1 changes its rate, top_edp outputs the wrong rate.
> - eDP display is garbled
>
> To solve this issue, remove all TVDPLL1 parents from `top_dp` and
> all TVDPLL2 parents from `top_edp`, plus, necessarily switch both
> clocks to use the new MUX_GATE_CLR_SET_UPD_INDEXED() macro to be
> able to use the right bit index for the new parents list.
>
> Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
> ---
> drivers/clk/mediatek/clk-mt8195-topckgen.c | 22 ++++++++++++++--------
> 1 file changed, 14 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/clk/mediatek/clk-mt8195-topckgen.c b/drivers/clk/mediatek/clk-mt8195-topckgen.c
> index 81daa24cadde..abb3721f6e1b 100644
> --- a/drivers/clk/mediatek/clk-mt8195-topckgen.c
> +++ b/drivers/clk/mediatek/clk-mt8195-topckgen.c
> @@ -417,15 +417,21 @@ static const char * const pwrmcu_parents[] = {
>
> static const char * const dp_parents[] = {
> "clk26m",
> - "tvdpll1_d2",
> "tvdpll2_d2",
> - "tvdpll1_d4",
> "tvdpll2_d4",
> - "tvdpll1_d8",
> "tvdpll2_d8",
> - "tvdpll1_d16",
> "tvdpll2_d16"
> };
> +static const u8 dp_parents_idx[] = { 0, 2, 4, 6, 8 };
> +
> +static const char * const edp_parents[] = {
> + "clk26m",
> + "tvdpll1_d2",
> + "tvdpll1_d4",
> + "tvdpll1_d8",
> + "tvdpll1_d16"
> +};
> +static const u8 edp_parents_idx[] = { 0, 1, 3, 5, 7 };
AFAII your solution is to force a specific TVDPLLX for each display, and
it isn't dynamic.
Do you think it's possible to do that using the DTS ? I'm asking
because, IMHO, this kind of setup is more friendly/readable/flexible in
the DTS than hardcoded into the driver.
>
> static const char * const disp_pwm_parents[] = {
> "clk26m",
> @@ -957,11 +963,11 @@ static const struct mtk_mux top_mtk_muxes[] = {
> MUX_GATE_CLR_SET_UPD_FLAGS(CLK_TOP_PWRMCU, "top_pwrmcu",
> pwrmcu_parents, 0x08C, 0x090, 0x094, 16, 3, 23, 0x08, 6,
> CLK_IS_CRITICAL | CLK_SET_RATE_PARENT),
> - MUX_GATE_CLR_SET_UPD(CLK_TOP_DP, "top_dp",
> - dp_parents, 0x08C, 0x090, 0x094, 24, 4, 31, 0x08, 7),
> + MUX_GATE_CLR_SET_UPD_INDEXED(CLK_TOP_DP, "top_dp",
> + dp_parents, dp_parents_idx, 0x08C, 0x090, 0x094, 24, 4, 31, 0x08, 7),
> /* CLK_CFG_10 */
> - MUX_GATE_CLR_SET_UPD(CLK_TOP_EDP, "top_edp",
> - dp_parents, 0x098, 0x09C, 0x0A0, 0, 4, 7, 0x08, 8),
> + MUX_GATE_CLR_SET_UPD_INDEXED(CLK_TOP_EDP, "top_edp",
> + edp_parents, edp_parents_idx, 0x098, 0x09C, 0x0A0, 0, 4, 7, 0x08, 8),
> MUX_GATE_CLR_SET_UPD(CLK_TOP_DPI, "top_dpi",
> dp_parents, 0x098, 0x09C, 0x0A0, 8, 4, 15, 0x08, 9),
> MUX_GATE_CLR_SET_UPD(CLK_TOP_DISP_PWM0, "top_disp_pwm0",
--
Regards,
Alexandre
next prev parent reply other threads:[~2023-07-13 13:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 7:21 [PATCH 0/2] MediaTek clocks: Support mux indices list and 8195 DP AngeloGioacchino Del Regno
2023-07-13 7:21 ` [PATCH 1/2] clk: mediatek: clk-mux: Support custom parent indices for muxes AngeloGioacchino Del Regno
2023-07-18 8:37 ` Alexandre Mergnat
2023-07-13 7:21 ` [PATCH 2/2] clk: mediatek: mt8195-topckgen: Refactor parents for top_dp/edp muxes AngeloGioacchino Del Regno
2023-07-13 13:22 ` Alexandre Mergnat [this message]
2023-07-14 4:19 ` Chen-Yu Tsai
2023-07-17 7:48 ` Maxime Ripard
2023-07-17 9:13 ` AngeloGioacchino Del Regno
2023-07-17 11:24 ` Maxime Ripard
2023-07-17 14:30 ` AngeloGioacchino Del Regno
2023-07-18 8:37 ` Alexandre Mergnat
2023-07-18 9:03 ` Maxime Ripard
2023-10-04 16:29 ` AngeloGioacchino Del Regno
2023-10-05 7:49 ` Alexandre Mergnat
2023-10-06 10:05 ` Maxime Ripard
2023-07-14 9:21 ` AngeloGioacchino Del Regno
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=9a0817c2-4101-5c21-977d-77ac0d83a067@baylibre.com \
--to=amergnat@baylibre.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=kernel@collabora.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=miles.chen@mediatek.com \
--cc=msp@baylibre.com \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
--cc=wenst@chromium.org \
--cc=yangyingliang@huawei.com \
/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
all inboxes | Powered by JetHome®