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 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, but I'm currently struggling with the last patch where we migrate the msm driver. It runs into a runtime PM problem where the parent device isn't runtime PM enabled yet. I'm still trying to figure out a clean solution there. Moving runtime PM around breaks boot and I think that's because the power domain is off. Cc: Daniel Vetter <daniel.vetter@xxxxxxxx> Cc: "Rafael J. Wysocki" <rafael@xxxxxxxxxx> Cc: Rob Clark <robdclark@xxxxxxxxx> Cc: Russell King <rmk+kernel@xxxxxxxxxxxxxxxx> Cc: Saravana Kannan <saravanak@xxxxxxxxxx> [1] https://lore.kernel.org/r/20210508074118.1621729-1-swboyd@xxxxxxxxxxxx Stephen Boyd (7): component: Drop 'dev' argument to component_match_realloc() component: Rename 'dev' to 'parent' component: Introduce struct aggregate_device component: Introduce the aggregate bus_type component: Use dev.parent instead of adev->parent component: Move struct aggregate_device out to header file drm/msm: Migrate to aggregate driver drivers/base/component.c | 614 ++++++++++++++++++++++------------ drivers/gpu/drm/msm/msm_drv.c | 47 +-- include/linux/component.h | 73 +++- 3 files changed, 487 insertions(+), 247 deletions(-) base-commit: 6efb943b8616ec53a5e444193dccf1af9ad627b5 -- https://chromeos.dev
