diff options
| author | Michal Simek <michal.simek@xilinx.com> | 2022-02-07 10:27:37 +0100 |
|---|---|---|
| committer | Michal Simek <michal.simek@xilinx.com> | 2022-02-15 13:01:42 +0100 |
| commit | e0283cbdfd49a437ef3cfdd662b196d2f70b5ea0 (patch) | |
| tree | d845cd6b699bc029289a76bda1d065234a24c1ba /MAINTAINERS | |
| parent | 2f9dd4bfc7a2d618c9c76448dd7b3ce67c6ec4ce (diff) | |
| download | u-boot-e0283cbdfd49a437ef3cfdd662b196d2f70b5ea0.zip u-boot-e0283cbdfd49a437ef3cfdd662b196d2f70b5ea0.tar.gz u-boot-e0283cbdfd49a437ef3cfdd662b196d2f70b5ea0.tar.bz2 | |
power: zynqmp: Add power domain driver for ZynqMP
Driver should be enabled by CONFIG_POWER_DOMAIN=y and
CONFIG_ZYNQMP_POWER_DOMAIN=y. Power domain driver doesn't have own DT node
but it uses zynqmp firmware DT node that's why there is a need to bind
driver when firmware node is found.
Driver itself is simple. It is sending pmufw config object overlay for
enabling access to device which is done in ...domain_request().
In ...domain_on() capabilities are passed and node is requested.
This should be bare minimum of required to get power domain driver working.
Signed-off-by: Michal Simek <michal.simek@xilinx.com>
Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
Link: https://lore.kernel.org/r/f4b9433b91c0b18c375b061c7a4e29d428f70547.1644226055.git.michal.simek@xilinx.com
Diffstat (limited to 'MAINTAINERS')
| -rw-r--r-- | MAINTAINERS | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/MAINTAINERS b/MAINTAINERS index dcdd99e..8bcdea2 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -634,6 +634,7 @@ F: drivers/mtd/nand/raw/zynq_nand.c F: drivers/net/phy/xilinx_phy.c F: drivers/net/zynq_gem.c F: drivers/phy/phy-zynqmp.c +F: drivers/power/domain/zynqmp-power-domain.c F: drivers/serial/serial_zynq.c F: drivers/reset/reset-zynqmp.c F: drivers/rtc/zynqmp_rtc.c |