| 1 | |
| 2 | %YAML 1.2
|
| 3 | ---
|
| 4 | $id: http://devicetree.org/schemas/interrupt-controller/msi-controller.yaml#
|
| 5 | $schema: http://devicetree.org/meta-schemas/core.yaml#
|
| 6 |
|
| 7 | title: MSI controller
|
| 8 |
|
| 9 | maintainers:
|
| 10 | - Marc Zyngier <[email protected]>
|
| 11 |
|
| 12 | description: |
|
| 13 | An MSI controller signals interrupts to a CPU when a write is made
|
| 14 | to an MMIO address by some master. An MSI controller may feature a
|
| 15 | number of doorbells.
|
| 16 |
|
| 17 | properties:
|
| 18 | "#msi-cells":
|
| 19 | description: |
|
| 20 | The number of cells in an msi-specifier, required if not zero.
|
| 21 |
|
| 22 | Typically this will encode information related to sideband data,
|
| 23 | and will not encode doorbells or payloads as these can be
|
| 24 | configured dynamically.
|
| 25 |
|
| 26 | The meaning of the msi-specifier is defined by the device tree
|
| 27 | binding of the specific MSI controller.
|
| 28 | enum: [0, 1]
|
| 29 |
|
| 30 | msi-controller:
|
| 31 | description:
|
| 32 | Identifies the node as an MSI controller.
|
| 33 | $ref: /schemas/types.yaml#/definitions/flag
|
| 34 |
|
| 35 | msi-ranges:
|
| 36 | description:
|
| 37 | A list of <phandle intspec span> tuples, where "phandle" is the
|
| 38 | parent interrupt controller, "intspec" is the starting/base
|
| 39 | interrupt specifier and "span" is the size of the
|
| 40 | range. Multiple ranges can be provided.
|
| 41 | $ref: /schemas/types.yaml#/definitions/phandle-array
|
| 42 |
|
| 43 | dependencies:
|
| 44 | "#msi-cells": [ msi-controller ]
|
| 45 |
|
| 46 | additionalProperties: true
|