summaryrefslogtreecommitdiffstats
path: root/Documentation/devicetree/bindings/soc/imx/fsl,imx8mm-disp-blk-ctrl.yaml
diff options
context:
space:
mode:
authorLucas Stach <l.stach@pengutronix.de>2021-07-15 16:41:38 +0200
committerLucas Stach <l.stach@pengutronix.de>2021-07-21 22:25:58 +0200
commit4f909843fd3b0f0fa970d9f28b0c875811a1288b (patch)
tree1b87fdbf8e586416e5c99e7a3c09231da553e0a9 /Documentation/devicetree/bindings/soc/imx/fsl,imx8mm-disp-blk-ctrl.yaml
parent329c79f2809a73cfc477342208d06da8ae77f5e0 (diff)
downloadlinux-4f909843fd3b0f0fa970d9f28b0c875811a1288b.tar.gz
linux-4f909843fd3b0f0fa970d9f28b0c875811a1288b.tar.xz
soc: imx: add i.MX8M blk-ctrl driver
This adds a driver for the blk-ctrl blocks found in the i.MX8M* line of SoCs. The blk-ctrl is a top-level peripheral located in the various *MIX power domains and interacts with the GPC power controller to provide the peripherals in the power domain access to the NoC and ensures that those peripherals are properly reset when their respective power domain is brought back to life. Software needs to do different things to make the bus handshake happen after the the GPC *MIX domain is power up and before it is powered down. As the requirements are quite different between the various blk-ctrls there is a callback function provided to hook in the proper sequence. The peripheral domains are quite uniform, they handle the soft clock enables and resets in the blk-ctrl address space and sequencing with the upstream GPC power domains. Signed-off-by: Lucas Stach <l.stach@pengutronix.de> --- This commit includes the full code to drive the VPUMIX domain on the i.MX8MM, as the skeleton driver would probably be harder to review without the context provided by one blk-ctrl implementation. Other blk-ctrl implementations will follow, based on this overall structure.
Diffstat (limited to 'Documentation/devicetree/bindings/soc/imx/fsl,imx8mm-disp-blk-ctrl.yaml')
0 files changed, 0 insertions, 0 deletions