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

[Val Packett <val@packett.cool>]

On 5/12/26 5:52 PM, Akhil P Oommen wrote:
> With the introduction of sync_state in the genpd framework, any consumer
> device of GCC and GPUCC which is not bound to a driver will result in
> bootup warnings like below:
>
> [   24.362666] gcc-kaanapali 100000.clock-controller: sync_state() pending due to 3d37000.gmu
> [   24.371210] gxclkctl-kaanapali 3d64000.clock-controller: sync_state() pending due to 3d37000.gmu
> [   24.380268] gpucc-kaanapali 3d90000.clock-controller: sync_state() pending due to 3d37000.gmu
>
> To silence these warnings and also to have a proper state in driver core,
> attach a driver to the GMU and set it up as a component device for the drm
> master device.
>
> The first few patches are preparatory fixes and refactorings. And the
> final patch introduces a driver for GMU devices.
>
> Signed-off-by: Akhil P Oommen <akhilpo@oss.qualcomm.com> [..]

For the series:

Tested-by: Val Packett <val@packett.cool> # x1e80100-dell-latitude-7455

When I first saw this series I didn't think this was important, silence 
warnings whatever, but since a couple months ago deep suspend started 
randomly not completing (bouncing back as soon as everything got 
suspended) and I didn't know what it was… just now in #aarch64-laptops 
this was brought up again and turns out, yeah. It was bouncing back due 
to sync_state not completing for everything. This series actually makes 
suspend reliable again!


Thanks,
~val