summaryrefslogtreecommitdiff
path: root/tools/lib/python
diff options
context:
space:
mode:
authorMing Qian <ming.qian@oss.nxp.com>2026-09-21 19:03:34 +0900
committerUlf Hansson <ulfh@kernel.org>2026-09-23 13:38:52 +0200
commit51c2db3ef0cb89a49ab7f47a40efd5d5b074ce8d (patch)
tree8920928c6f2f28d6f23d9a66dae07cd1268220a3 /tools/lib/python
parentdf2908090cda368b01ff43709f51890076c56157 (diff)
downloadlinux-next-51c2db3ef0cb89a49ab7f47a40efd5d5b074ce8d.tar.gz
linux-next-51c2db3ef0cb89a49ab7f47a40efd5d5b074ce8d.zip
pmdomain: imx8m-blk-ctrl: Serialize power on/off across sibling domains
On i.MX8MP the VPU blk-ctrl exposes G1, G2 and VC8000E as three separate genpds, each serialized only by its own genpd lock, so their power_on and power_off callbacks can run concurrently on SMP. The sequences are not independent: they share the VPUMIX bus domain, the VPU_NOC and the ADB400 handshake. On power up the GPC cannot ack-verify the ADB400 handshake - the ack only completes once blk-ctrl sets the bus clk-en bit - so it just waits a fixed delay instead of polling hskack. A sibling transition landing inside another domain's reset window disturbs that shared clock and handshake timing, the victim's reset does not take effect, and its block registers read back all zeros: the decoder times out or the encoder fails its format check. Serialize the blk-ctrl reset sequence with a per-blk-ctrl mutex; the driver deliberately avoids a genpd hierarchy, so the genpd core gives no cross-sibling serialization. Fixes: a1a5f15f7f6c ("soc: imx: imx8m-blk-ctrl: add i.MX8MP VPU blk ctrl") Signed-off-by: Ming Qian <ming.qian@oss.nxp.com> Reviewed-by: Frank Li <Frank.Li@nxp.com> Cc: stable@vger.kernel.org Signed-off-by: Ulf Hansson <ulfh@kernel.org>
Diffstat (limited to 'tools/lib/python')
0 files changed, 0 insertions, 0 deletions