Skip to content

Commit dd3e3dc

Browse files
committed
schemas: pci: Add description for msi-map
Copy the remaining description from Linux kernel pci-msi.txt document. Signed-off-by: Rob Herring (Arm) <[email protected]>
1 parent 494b6d0 commit dd3e3dc

File tree

1 file changed

+26
-0
lines changed

1 file changed

+26
-0
lines changed

dtschema/schemas/pci/pci-host-bridge.yaml

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -32,6 +32,32 @@ properties:
3232
$ref: /schemas/types.yaml#/definitions/uint32
3333

3434
msi-map:
35+
description: >
36+
Maps a Requester ID (AKA RID) to an MSI controller and associated
37+
msi-specifier data.
38+
39+
Each PCI device under a root complex is uniquely identified by its
40+
Requester ID. A Requester ID is a triplet of a Bus number,
41+
Device number, and Function number.
42+
43+
For the purpose of this document, when treated as a numeric value, a RID
44+
is formatted such that:
45+
46+
* Bits [15:8] are the Bus number.
47+
* Bits [7:3] are the Device number.
48+
* Bits [2:0] are the Function number.
49+
* Any other bits required for padding must be zero.
50+
51+
MSIs may be distinguished in part through the use of sideband data
52+
accompanying writes. In the case of PCI devices, this sideband data may be
53+
derived from the Requester ID. A mechanism is required to associate a
54+
device with both the MSI controllers it can address, and the sideband data
55+
that will be associated with its writes to those controllers.
56+
57+
Any RID r in the interval [rid-base, rid-base + length) is associated with
58+
the listed msi-controller, with the msi-specifier (r - rid-base +
59+
msi-base).
60+
3561
$ref: /schemas/types.yaml#/definitions/uint32-matrix
3662
items:
3763
items:

0 commit comments

Comments
 (0)