vout: fix potential issue with vout frame rate calculation [1/1]

PD#SWPL-236564

Problem:
the logic for calculating the frame rate in vout is risky. the
reason it currently functions without issues is that the vdin
module also calls it and correctly configures the clk

Solution:
vdin_meas_clk_val needs to be assigned a value first, and
then it can be used for msr_ctrl_init

Verify:
t6x/t3x

Change-Id: Id76c7581aefb040a4ced30a8964c04f43d5f3532
Signed-off-by: congyang.huang <congyang.huang@amlogic.com>
This commit is contained in:
congyang.huang
2025-10-23 06:06:38 +00:00
committed by gerrit autosubmit
parent 581dcbda14
commit f054aaaaae
+3 -3
View File
@@ -610,12 +610,12 @@ static int vout_mux_probe(struct platform_device *pdev)
}
vout_mux_data = (struct vout_mux_data_s *)match->data;
if (is_meson_t3x_cpu() || is_meson_t6x_cpu())
vdin_meas_clk_val = VDIN_MEAS_CLK_FREQ_T3X;
if (vout_mux_data->msr_ctrl_init)
vout_mux_data->msr_ctrl_init(pdev, vout_mux_data);
if (is_meson_t3x_cpu())
vdin_meas_clk_val = VDIN_MEAS_CLK_FREQ_T3X;
VOUTPR("%s OK\n", __func__);
return 0;