On 04-07-19, 07:49, Leonard Crestez wrote: > On 7/4/2019 9:23 AM, Anson.Huang@xxxxxxx wrote: > > From: Anson Huang <Anson.Huang@xxxxxxx> > > > > Assign highest OPP as suspend OPP to reduce suspend/resume > > latency on i.MX8MM. > > > > Signed-off-by: Anson Huang <Anson.Huang@xxxxxxx> > > --- > > arch/arm64/boot/dts/freescale/imx8mm.dtsi | 1 + > > 1 file changed, 1 insertion(+) > > > > diff --git a/arch/arm64/boot/dts/freescale/imx8mm.dtsi b/arch/arm64/boot/dts/freescale/imx8mm.dtsi > > index b11fc5e..3a62407 100644 > > --- a/arch/arm64/boot/dts/freescale/imx8mm.dtsi > > +++ b/arch/arm64/boot/dts/freescale/imx8mm.dtsi > > @@ -136,6 +136,7 @@ > > opp-microvolt = <1000000>; > > opp-supported-hw = <0x8>, <0x3>; > > clock-latency-ns = <150000>; > > + opp-suspend; > > }; > > }; > > What if the highest OPP is unavailable due to speed grading? What does this exactly mean ? How is the OPP made unavailable in your case ? What will dev_pm_opp_get_suspend_opp_freq() return in this case ? > Ideally we > should find a way to suspend at the highest *supported* OPP. > > Maybe the opp-suspend marking could be assigned from imx-cpufreq-dt > driver code? Sorry for jumping in late, the latest patch from Anson drew my attention to this topic :) -- viresh
