threeeye
bc1d038eac
Squashed backup commit (no shallow-clone history issues) of xiaomi-mt6833-dev/kernel_xiaomi_mt6833 (lineage-23.2 branch, upstream commit 9eece662e) plus all fixes applied to get everpal_defconfig building clean against a modern (GCC 15.2.0) toolchain -- see the previous commit message on the lineage-23.2 branch (also in this repo history is not available here since this is a squashed snapshot; full incremental history lives in the local DL380 checkout and the upstream GitHub remote). Upstream: https://github.com/xiaomi-mt6833-dev/kernel_xiaomi_mt6833 (lineage-23.2)
45 lines
1.4 KiB
Plaintext
45 lines
1.4 KiB
Plaintext
|
|
* Marvell ODMI for MSI support
|
|
|
|
Some Marvell SoCs have an On-Die Message Interrupt (ODMI) controller
|
|
which can be used by on-board peripheral for MSI interrupts.
|
|
|
|
Required properties:
|
|
|
|
- compatible : The value here should contain:
|
|
|
|
"marvell,ap806-odmi-controller", "marvell,odmi-controller".
|
|
|
|
- interrupt,controller : Identifies the node as an interrupt controller.
|
|
|
|
- msi-controller : Identifies the node as an MSI controller.
|
|
|
|
- marvell,odmi-frames : Number of ODMI frames available. Each frame
|
|
provides a number of events.
|
|
|
|
- reg : List of register definitions, one for each
|
|
ODMI frame.
|
|
|
|
- marvell,spi-base : List of GIC base SPI interrupts, one for each
|
|
ODMI frame. Those SPI interrupts are 0-based,
|
|
i.e marvell,spi-base = <128> will use SPI #96.
|
|
See Documentation/devicetree/bindings/interrupt-controller/arm,gic.txt
|
|
for details about the GIC Device Tree binding.
|
|
|
|
- interrupt-parent : Reference to the parent interrupt controller.
|
|
|
|
Example:
|
|
|
|
odmi: odmi@300000 {
|
|
compatible = "marvell,ap806-odmi-controller",
|
|
"marvell,odmi-controller";
|
|
interrupt-controller;
|
|
msi-controller;
|
|
marvell,odmi-frames = <4>;
|
|
reg = <0x300000 0x4000>,
|
|
<0x304000 0x4000>,
|
|
<0x308000 0x4000>,
|
|
<0x30C000 0x4000>;
|
|
marvell,spi-base = <128>, <136>, <144>, <152>;
|
|
};
|