Quoting Vinod Polimera (2022-03-03 01:39:59)
Kernel clock driver assumes that initial rate is the max rate for that clock and was not allowing it to scale beyond the assigned clock value.
Drop the assigned clock rate property and vote on the mdp clock as per calculated value during the usecase.
Fixes: a3db7ad1af("arm64: dts: qcom: sc7180: add display dt nodes") Signed-off-by: Vinod Polimera quic_vpolimer@quicinc.com
Reviewed-by: Stephen Boyd swboyd@chromium.org