Quoting Daniel Vetter (2021-12-07 10:22:15)
On Thu, Dec 02, 2021 at 02:26:58PM -0800, Stephen Boyd wrote:
This series is from discussion we had on reordering the device lists for drm shutdown paths[1]. I've introduced an 'aggregate' bus that we put the aggregate device onto and then we probe the aggregate device once all the components are probed and call component_add(). The probe/remove hooks are where the bind/unbind calls go, and then a shutdown hook is added that can be used to shutdown the drm display pipeline at the right time.
This works for me on my sc7180 board. I no longer get a warning from i2c at shutdown that we're trying to make an i2c transaction after the i2c bus has been shutdown. There's more work to do on the msm drm driver to extract component device resources like clks, regulators, etc. out of the component bind function into the driver probe but I wanted to move everything over now in other component drivers before tackling that problem.
Tested-by tags would be appreciated, and Acked-by/Reviewed-by tags too.
Thanks for pushing this forward. Unfortunately I'm completely burried and it's just not improving, so merge plan:
please get Greg KH to ack the bus/driver core stuff
please get one of the drm-misc committers we have from Google's Chromeos team (there should be a few by now) to review&push this.
Sounds like a plan. Thanks!
Otherwise I fear this might get stuck and I'd really like to avoid that.