Commit c1e213e5 authored by Ulf Hansson's avatar Ulf Hansson

genpd: Create a new subsystem directory to host genpd providers

There are currently ~60 users of the genpd provider interface, which
implementations are sprinkled across various subsystems. To simplify with
maintenance let's create a new subsystem (drivers/genpd) and start moving
the providers in there.

My intention is also to host a git tree to collect and to get the patches
tested/integrated through the linux-next tree. Ideally this should release
some of the burden on the soc maintainers.

Note that, I will of course require acks/reviews from the current platform
maintainers, hence the MAINTAINERS file needs to be updated accordingly for
each genpd provider that is moved into the new genpd subsystem.
Signed-off-by: default avatarUlf Hansson <ulf.hansson@linaro.org>
parent 06c2afb8
...@@ -8665,6 +8665,13 @@ F: Documentation/devicetree/bindings/power/power?domain* ...@@ -8665,6 +8665,13 @@ F: Documentation/devicetree/bindings/power/power?domain*
F: drivers/base/power/domain*.c F: drivers/base/power/domain*.c
F: include/linux/pm_domain.h F: include/linux/pm_domain.h
GENERIC PM DOMAIN PROVIDERS
M: Ulf Hansson <ulf.hansson@linaro.org>
L: linux-pm@vger.kernel.org
S: Supported
T: git git://git.kernel.org/pub/scm/linux/kernel/git/ulfh/linux-pm.git
F: drivers/genpd/
GENERIC RESISTIVE TOUCHSCREEN ADC DRIVER GENERIC RESISTIVE TOUCHSCREEN ADC DRIVER
M: Eugen Hristev <eugen.hristev@microchip.com> M: Eugen Hristev <eugen.hristev@microchip.com>
L: linux-input@vger.kernel.org L: linux-input@vger.kernel.org
......
...@@ -45,6 +45,7 @@ obj-$(CONFIG_DMADEVICES) += dma/ ...@@ -45,6 +45,7 @@ obj-$(CONFIG_DMADEVICES) += dma/
# SOC specific infrastructure drivers. # SOC specific infrastructure drivers.
obj-y += soc/ obj-y += soc/
obj-$(CONFIG_PM_GENERIC_DOMAINS) += genpd/
obj-y += virtio/ obj-y += virtio/
obj-$(CONFIG_VDPA) += vdpa/ obj-$(CONFIG_VDPA) += vdpa/
......
# SPDX-License-Identifier: GPL-2.0-only
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment