The PCI bus device tree supports 'ranges' properties that indicate how to
convert PCI addresses to CPU addresses. Many PCI controllers are dual-role
controllers, supporting both Root Complex (RC) and Endpoint (EP) modes. The
EP side also needs similar information for proper address translation.
Add 'ranges' property for pcie-ep, which format is same as PCI's ranges.
Signed-off-by: Frank Li <Frank.Li@xxxxxxx>
---
Documentation/devicetree/bindings/pci/pci-ep.yaml | 30 +++++++++++++++++++++++
1 file changed, 30 insertions(+)
diff --git a/Documentation/devicetree/bindings/pci/pci-ep.yaml b/Documentation/devicetree/bindings/pci/pci-ep.yaml
index f75000e3093db..2de00d2bf7326 100644
--- a/Documentation/devicetree/bindings/pci/pci-ep.yaml
+++ b/Documentation/devicetree/bindings/pci/pci-ep.yaml
@@ -17,6 +17,26 @@ properties:
$nodename:
pattern: "^pcie-ep@"
+ ranges:
+ description:
+ Outbound memory regions, which is extend reg 'addr_space' if pci bus
+ address is not equal cpu address or there are more one outbound
+ memory regions.
+ oneOf:
+ - type: boolean
+ - minItems: 1
+ maxItems: 32 # Should be enough
+ items:
+ minItems: 5
+ maxItems: 8
+ additionalItems: true
+ items:
+ - enum:
+ - 0x42000000
+ - 0x43000000
+ - 0x82000000
+ - 0x83000000
+
max-functions:
description: Maximum number of functions that can be configured
$ref: /schemas/types.yaml#/definitions/uint8
@@ -42,6 +62,16 @@ properties:
default: 1
maximum: 16
+ device_type:
+ $ref: /schemas/types.yaml#/definitions/string
+ const: pci-ep
+
+ "#address-cells":
+ const: 3
+
+ "#size-cells":
+ const: 2
+
linux,pci-domain:
description:
If present this property assigns a fixed PCI domain number to a PCI
--
2.34.1
