[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAE-0n52OPUEMO4iXP_6LuRcN5r+v-9oZoRwij_y+bwnUBC3ohw@mail.gmail.com>
Date: Fri, 25 Feb 2022 10:06:15 -0800
From: Stephen Boyd <swboyd@...omium.org>
To: Vinod Polimera <quic_vpolimer@...cinc.com>,
devicetree@...r.kernel.org, dri-devel@...ts.freedesktop.org,
freedreno@...ts.freedesktop.org, linux-arm-msm@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, robdclark@...il.com,
dianders@...omium.org, quic_kalyant@...cinc.com
Subject: Re: [PATCH v2 1/2] arm64/dts/qcom/sc7280: remove assigned-clock-rate
property for mdp clk
Quoting Vinod Polimera (2022-02-25 07:57:49)
> 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 set it
> during resume sequence with max value in the opp table.
>
> Fixes: 62fbdce91("arm64: dts: qcom: sc7280: add display dt nodes")
>
There shouldn't be a newline here. The fixes tag should be directly
attached to the SoB area.
> Signed-off-by: Vinod Polimera <quic_vpolimer@...cinc.com>
> ---
> arch/arm64/boot/dts/qcom/sc7280.dtsi | 9 ++-------
Can you also update sc7180.dtsi? Are there others SoCs that need an
update because they're using an OPP table?
Doesn't this need to come after the driver change?
Powered by blists - more mailing lists