aboutsummaryrefslogtreecommitdiff
path: root/scripts/gdb/linux/utils.py
diff options
context:
space:
mode:
authorTony Lindgren <[email protected]>2021-09-30 11:30:03 +0300
committerTony Lindgren <[email protected]>2021-09-30 11:30:03 +0300
commitb232537074fcaf0c2837abbb217429c097bb7598 (patch)
tree61b4fc6bd6cc8e5e5bd7ce2304be1bc5c7e94552 /scripts/gdb/linux/utils.py
parent6880fa6c56601bb8ed59df6c30fd390cc5f6dd8f (diff)
soc: ti: omap-prm: Fix external abort for am335x pruss
Starting with v5.15-rc1, we may now see some am335x beaglebone black device produce the following error on pruss probe: Unhandled fault: external abort on non-linefetch (0x1008) at 0xe0326000 This has started with the enabling of pruss for am335x in the dts files. Turns out the is caused by the PRM reset handling not waiting for the reset bit to clear. To fix the issue, let's always wait for the reset bit to clear, even if there is a separate reset status register. We attempted to fix a similar issue for dra7 iva with a udelay() in commit effe89e40037 ("soc: ti: omap-prm: Fix occasional abort on reset deassert for dra7 iva"). There is no longer a need for the udelay() for dra7 iva reset either with the check added for reset bit clearing. Cc: Drew Fustini <[email protected]> Cc: Grygorii Strashko <[email protected]> Cc: "H. Nikolaus Schaller" <[email protected]> Cc: Robert Nelson <[email protected]> Cc: Yongqin Liu <[email protected]> Fixes: effe89e40037 ("soc: ti: omap-prm: Fix occasional abort on reset deassert for dra7 iva") Reported-by: Matti Vaittinen <[email protected]> Tested-by: Matti Vaittinen <[email protected]> Signed-off-by: Tony Lindgren <[email protected]>
Diffstat (limited to 'scripts/gdb/linux/utils.py')
0 files changed, 0 insertions, 0 deletions