The avs drivers in drivers/power/avs/* are all SoC specific drivers that doesn't share any code. Instead they are located in a directory, mostly to keep similar functionality together. From a maintenance point of view, it makes better sense to collect SoC specific drivers like these, into the SoC specific directories.
Therefore, this series moves the drivers, one by one - and in the end, it deletes the empty avs directory. It seems best to me, if this can be funneled via Rafael's linux-pm tree. Then when going forward, each driver should be managed through the SoC maintainer's trees. Kind regards Ulf Hansson Ulf Hansson (4): power: avs: qcom-cpr: Move the driver to the qcom specific drivers power: avs: rockchip-io: Move the driver to the rockchip specific drivers power: avs: smartreflex Move driver to soc specific drivers power: avs: Drop the avs directory and the corresponding Kconfig MAINTAINERS | 6 +-- arch/arm/plat-omap/Kconfig | 2 +- drivers/power/Kconfig | 1 - drivers/power/Makefile | 1 - drivers/power/avs/Kconfig | 37 ------------------- drivers/power/avs/Makefile | 4 -- drivers/soc/qcom/Kconfig | 16 ++++++++ drivers/soc/qcom/Makefile | 1 + .../{power/avs/qcom-cpr.c => soc/qcom/cpr.c} | 0 drivers/soc/rockchip/Kconfig | 8 ++++ drivers/soc/rockchip/Makefile | 1 + .../rockchip/io-domain.c} | 0 drivers/soc/ti/Makefile | 1 + drivers/{power/avs => soc/ti}/smartreflex.c | 0 14 files changed, 31 insertions(+), 47 deletions(-) delete mode 100644 drivers/power/avs/Kconfig delete mode 100644 drivers/power/avs/Makefile rename drivers/{power/avs/qcom-cpr.c => soc/qcom/cpr.c} (100%) rename drivers/{power/avs/rockchip-io-domain.c => soc/rockchip/io-domain.c} (100%) rename drivers/{power/avs => soc/ti}/smartreflex.c (100%) -- 2.25.1