Re: [PATCH] arm64: dts: qcom: hamoa: Fix OPP tables for all DisplayPort controllers

[Dmitry Baryshkov]

On Tue, Mar 17, 2026 at 03:39:34PM +0530, Viresh Kumar wrote:
> On 16-03-26, 21:38, Dmitry Baryshkov wrote:
> > I was sure that DT bindings mandate it. However, the bindings don't
> > include anything supporting that definition. It simply says:
> >   Devices work at voltage-current-frequency combinations and some
> >   implementations have the liberty of choosing these.
> > 
> > Viresh, what is the more exact interpretation? If we have a valid rate
> > for which all other params match the other defined OPP, should we still
> > define that in the table?
> 
> The frequency in the OPP table entry is the highest frequency at which the
> properties apply. You don't need duplicate entries in the OPP table if rest of
> the properties are same. If you look at dev_pm_opp_set_rate(), it preserves the
> frequency passed to it (well modifies it with the return value of round-rate),
> which is then used to set the clock eventually. The opp-rate isn't directly
> used.

Ack, thanks!

So we can drop 19.2 corner (and 192 ofc) and we don't need 162 corner.

-- 
With best wishes
Dmitry