Quoting Bjorn Andersson (2022-06-30 21:00:11) > On Tue 28 Jun 15:13 CDT 2022, Stephen Boyd wrote: > > > Tracking down what RPMh resource is blocking XO shutdown in suspend is > > hard. Largely because we need external debug tools to dump the RPMh > > internal state to figure out what resource is enabled. Instead of doing > > that, let's just block system wide suspend in the kernel if the RPMh XO > > resource is enabled by something in the kernel. This will help us narrow > > down XO shutdown failures to the XO clk, and not something else like an > > interconnect or regulator RPMh resource. > > > > I'm sending this as an RFC because it breaks suspend for me on Trogdor > > boards. I found out that the XO resource is always enabled on these > > devices because the audio driver leaves an audio clk always on. This > > means that the XO resource must not be used to determine if XO shutdown > > is achievable, or we're leaving power savings on the table. > > > > Cc: Taniya Das <quic_tdas@xxxxxxxxxxx> > > Cc: Mike Tipton <quic_mdtipton@xxxxxxxxxxx> > > Signed-off-by: Stephen Boyd <swboyd@xxxxxxxxxxxx> > > Reviewed-by: Bjorn Andersson <bjorn.andersson@xxxxxxxxxx> > > > --- > > > > Please don't apply. It will break suspend on Trogdor boards. > > > > This seems like a useful debug feature for people outside of Qualcomm, > so I assume you're saying that we shouldn't merge it until someone has > fixed the audio driver? Or did you post it just as a debug tool? > I mainly posted it to get a response from Qualcomm on what's going on. I haven't tried to fix the audio driver so far, but I can certainly look into it. The audio clk driver keeping XO on doesn't seem to matter for power because we're hitting the deepest of sleeps on Trogdor boards. I also realized that due to clk adoption logic we can't be certain that this driver's suspend function will be called after other clk providers that consume XO run their suspend functions. We can probably assume clk consumers that aren't providers will probe after clk-rpmh, so this check is generally safe because we don't have clk providers disabling clks during their suspend functions. It's just not totally safe. Maybe this is a good reason to add some sort of suspend op to clk_ops and then call that during system wide suspend.
