diff options
author | Rob Herring <[email protected]> | 2021-09-24 16:42:21 -0500 |
---|---|---|
committer | Sudeep Holla <[email protected]> | 2021-09-26 15:33:30 +0100 |
commit | 319aeaf69c85dc39768b3754c1786225e38e2871 (patch) | |
tree | 2fa12db84ecec9ff9a5616162ec91199268fb009 /scripts/gdb/linux/utils.py | |
parent | 078fb7aa6a8305bce09cdfbe77b4c987934442ba (diff) |
arm: dts: vexpress: Fix motherboard bus 'interrupt-map'
Commit 078fb7aa6a83 ("arm: dts: vexpress: Fix addressing issues with
'motherboard-bus' nodes") broke booting on a couple of 32-bit VExpress
boards. The problem is #address-cells size changed, but interrupt-map
was not updated. This results in the timer interrupt (and all the
other motherboard interrupts) not getting mapped.
As the 'interrupt-map' properties are all just duplicates across boards,
just move them into vexpress-v2m.dtsi and vexpress-v2m-rs1.dtsi.
Strictly speaking, 'interrupt-map' is dependent on the parent
interrupt controller, but it's not likely we'll ever have a different
parent than GICv2 on these old platforms. If there was one,
'interrupt-map' can still be overridden.
Link: https://lore.kernel.org/r/[email protected]
Fixes: 078fb7aa6a83 ("arm: dts: vexpress: Fix addressing issues with 'motherboard-bus' nodes")
Cc: Guillaume Tucker <[email protected]>
Cc: Liviu Dudau <[email protected]>
Cc: Sudeep Holla <[email protected]>
Cc: Lorenzo Pieralisi <[email protected]>
Cc: [email protected]
Reported-by: Reported-by: "kernelci.org bot" <[email protected]>
Signed-off-by: Rob Herring <[email protected]>
Signed-off-by: Sudeep Holla <[email protected]>
Diffstat (limited to 'scripts/gdb/linux/utils.py')
0 files changed, 0 insertions, 0 deletions