Lines Matching +full:memory +full:- +full:controllers

1 This document describes the generic device tree binding for MSI controllers and
9 those busses to the MSI controllers which they are capable of using,
14 - The doorbell (the MMIO address written to).
19 - The payload (the value written to the doorbell).
22   MSI controllers may have restrictions on permitted payloads.
24 - Sideband information accompanying the write.
27   taken through the memory system (i.e. it is a property of the combination of
31 MSI controllers:
38 --------------------
40 - msi-controller: Identifies the node as an MSI controller.
43 --------------------
45 - #msi-cells: The number of cells in an msi-specifier, required if not zero.
50   The meaning of the msi-specifier is defined by the device tree binding of
62 --------------------
64 - msi-parent: A list of phandle + msi-specifier pairs, one for each MSI
68   MSI controllers listed in the msi-parent property.
73   When #msi-cells is non-zero, busses with an msi-parent will require
82 	#address-cells = <1>;
83 	#size-cells = <1>;
85 	msi_a: msi-controller@a {
87 		compatible = "vendor-a,some-controller";
88 		msi-controller;
89 		/* No sideband data, so #msi-cells omitted */
92 	msi_b: msi-controller@b {
94 		compatible = "vendor-b,another-controller";
95 		msi-controller;
97 		#msi-cells = <1>;
100 	msi_c: msi-controller@c {
102 		compatible = "vendor-b,another-controller";
103 		msi-controller;
105 		#msi-cells = <1>;
110 		compatible = "vendor-c,some-device";
113 		msi-parent = <&msi_a>;
118 		compatible = "vendor-c,some-device";
123 		msi-parent = <&msi_a>, <&msi_b 0x17>;
128 		compatible = "vendor-c,some-device";
131 		 * Can generate MSIs to all of the MSI controllers.
133 		msi-parent = <&msi_a>, <&msi_b 0x17>, <&msi_c 0x53>;