Re: [PATCH RFT 0/5] drm/msm: Attach a driver to GMU

[Val Packett]

On 10/17/26 7:03 AM, Vladyslav Tymoshchuk wrote:
> Hi Akhil,
>
> On Sun, 26 Jul 2026 21:35:35 +0530, Akhil P Oommen wrote:
> > I didn't get a chance to revisit this series after my vacation. I am too
> > not aware of any impact outside of those dmesg warnings. Any chance this
> > recent rpmh related fix is helping with the deep sleep instead of this
> > series:
> >
> > https://lore.kernel.org/lkml/20260605-assorted-fixes-june-v1-1-2caa04f7287c@xxxxxxxxxxxxxxxx/

Update: the "deep" suspend bounce back was a red herring, it's actually 
related to EL2 timer nonsense btw.

In terms of actually reaching AOSD/CXSD states though, new community 
research has been happening recently (on hamoa laptops), and some people 
have gotten to CXSD buuuuut, with CONFIG_FW_DEVLINK_SYNC_STATE_TIMEOUT=y 
(aka fw_devlink.sync_state=timeout at cmdline).

It's not good to require timeouts, there should not be any sync_state 
warnings. With QCE solved now in the "Fix crypto self-test failures" 
series, the *only* sync_state timeouts are the GMU (on gcc and gpucc) 
and CoreSight stuff (on qcom_aoss_qmp). These can, and should, be resolved!


Thanks,
~val