diff options
author | Konrad Dybcio <[email protected]> | 2023-11-27 16:52:13 +0100 |
---|---|---|
committer | Thomas Gleixner <[email protected]> | 2023-12-12 15:40:42 +0100 |
commit | 221b110d87c2d3ea113ad784b2c6505726a3e157 (patch) | |
tree | e554fdbd265bc1ed84851cedcb1217bc059eea66 /lib/test_fortify/write_overflow-strncpy-src.c | |
parent | ca596295f4c9ec803d3379635ad175897993f121 (diff) |
irqchip/qcom-mpm: Support passing a slice of SRAM as reg space
The MPM hardware is accessible from the ARM CPUs through a shared memory
region (RPM MSG RAM) which is also concurrently accessed by other kinds of
cores on the system like modem, ADSP etc.
Modeling this relation in a (somewhat) sane manner in the device tree
requires to
- either present the MPM as a child of said memory region, which
makes little sense, as a mapped memory carveout is not a bus.
- define nodes which bleed their register spaces into one another
- or passing their slice of the MSG RAM through a property
Go with the third option and add a way to map a region passed through the
"qcom,rpm-msg-ram" property as register space for the MPM interrupt
controller.
The current way of using 'reg' is preserved for backwards compatibility
reasons.
[ tglx: Massaged changelog ]
Signed-off-by: Konrad Dybcio <[email protected]>
Signed-off-by: Thomas Gleixner <[email protected]>
Reviewed-by: Bryan O'Donoghue <[email protected]>
Acked-by: Shawn Guo <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Diffstat (limited to 'lib/test_fortify/write_overflow-strncpy-src.c')
0 files changed, 0 insertions, 0 deletions