Re: [PATCH v4] dt-bindings: misc: convert fsl,qoriq-mc from txt to YAML
On Mon, 23 Nov 2020 11:00:35 +0200, Laurentiu Tudor wrote: > From: Ionut-robert Aron > > Convert fsl,qoriq-mc to YAML in order to automate the verification > process of dts files. In addition, update MAINTAINERS accordingly > and, while at it, add some missing files. > > Signed-off-by: Ionut-robert Aron > [laurentiu.tu...@nxp.com: update MINTAINERS, updates & fixes in schema] > Signed-off-by: Laurentiu Tudor > --- > Changes in v4: > - use $ref to point to fsl,qoriq-mc-dpmac binding > > Changes in v3: > - dropped duplicated "fsl,qoriq-mc-dpmac" schema and replaced with >reference to it > - fixed a dt_binding_check warning > > Changes in v2: > - fixed errors reported by yamllint > - dropped multiple unnecessary quotes > - used schema instead of text in description > - added constraints on dpmac reg property > > .../devicetree/bindings/misc/fsl,qoriq-mc.txt | 196 -- > .../bindings/misc/fsl,qoriq-mc.yaml | 186 + > .../ethernet/freescale/dpaa2/overview.rst | 5 +- > MAINTAINERS | 4 +- > 4 files changed, 193 insertions(+), 198 deletions(-) > delete mode 100644 Documentation/devicetree/bindings/misc/fsl,qoriq-mc.txt > create mode 100644 Documentation/devicetree/bindings/misc/fsl,qoriq-mc.yaml > As there's a dependency on fsl,qoriq-mc-dpmac, this needs to go via netdev tree. Reviewed-by: Rob Herring
Re: [PATCH v4] dt-bindings: misc: convert fsl,qoriq-mc from txt to YAML
On Mon, Nov 23, 2020 at 11:00:35AM +0200, Laurentiu Tudor wrote: > From: Ionut-robert Aron > > Convert fsl,qoriq-mc to YAML in order to automate the verification > process of dts files. In addition, update MAINTAINERS accordingly > and, while at it, add some missing files. > > Signed-off-by: Ionut-robert Aron > [laurentiu.tu...@nxp.com: update MINTAINERS, updates & fixes in schema] > Signed-off-by: Laurentiu Tudor Acked-by: Ioana Ciornei > --- > Changes in v4: > - use $ref to point to fsl,qoriq-mc-dpmac binding > > Changes in v3: > - dropped duplicated "fsl,qoriq-mc-dpmac" schema and replaced with >reference to it > - fixed a dt_binding_check warning > > Changes in v2: > - fixed errors reported by yamllint > - dropped multiple unnecessary quotes > - used schema instead of text in description > - added constraints on dpmac reg property > > .../devicetree/bindings/misc/fsl,qoriq-mc.txt | 196 -- > .../bindings/misc/fsl,qoriq-mc.yaml | 186 + > .../ethernet/freescale/dpaa2/overview.rst | 5 +- > MAINTAINERS | 4 +- > 4 files changed, 193 insertions(+), 198 deletions(-) > delete mode 100644 Documentation/devicetree/bindings/misc/fsl,qoriq-mc.txt > create mode 100644 Documentation/devicetree/bindings/misc/fsl,qoriq-mc.yaml > > diff --git a/Documentation/devicetree/bindings/misc/fsl,qoriq-mc.txt > b/Documentation/devicetree/bindings/misc/fsl,qoriq-mc.txt > deleted file mode 100644 > index 7b486d4985dc.. > --- a/Documentation/devicetree/bindings/misc/fsl,qoriq-mc.txt > +++ /dev/null > @@ -1,196 +0,0 @@ > -* Freescale Management Complex > - > -The Freescale Management Complex (fsl-mc) is a hardware resource > -manager that manages specialized hardware objects used in > -network-oriented packet processing applications. After the fsl-mc > -block is enabled, pools of hardware resources are available, such as > -queues, buffer pools, I/O interfaces. These resources are building > -blocks that can be used to create functional hardware objects/devices > -such as network interfaces, crypto accelerator instances, L2 switches, > -etc. > - > -For an overview of the DPAA2 architecture and fsl-mc bus see: > -Documentation/networking/device_drivers/ethernet/freescale/dpaa2/overview.rst > - > -As described in the above overview, all DPAA2 objects in a DPRC share the > -same hardware "isolation context" and a 10-bit value called an ICID > -(isolation context id) is expressed by the hardware to identify > -the requester. > - > -The generic 'iommus' property is insufficient to describe the relationship > -between ICIDs and IOMMUs, so an iommu-map property is used to define > -the set of possible ICIDs under a root DPRC and how they map to > -an IOMMU. > - > -For generic IOMMU bindings, see > -Documentation/devicetree/bindings/iommu/iommu.txt. > - > -For arm-smmu binding, see: > -Documentation/devicetree/bindings/iommu/arm,smmu.yaml. > - > -The MSI writes are accompanied by sideband data which is derived from the > ICID. > -The msi-map property is used to associate the devices with both the ITS > -controller and the sideband data which accompanies the writes. > - > -For generic MSI bindings, see > -Documentation/devicetree/bindings/interrupt-controller/msi.txt. > - > -For GICv3 and GIC ITS bindings, see: > -Documentation/devicetree/bindings/interrupt-controller/arm,gic-v3.yaml. > - > -Required properties: > - > -- compatible > -Value type: > -Definition: Must be "fsl,qoriq-mc". A Freescale Management Complex > -compatible with this binding must have Block Revision > -Registers BRR1 and BRR2 at offset 0x0BF8 and 0x0BFC in > -the MC control register region. > - > -- reg > -Value type: > -Definition: A standard property. Specifies one or two regions > -defining the MC's registers: > - > - -the first region is the command portal for the > -this machine and must always be present > - > - -the second region is the MC control registers. This > -region may not be present in some scenarios, such > -as in the device tree presented to a virtual machine. > - > -- ranges > -Value type: > -Definition: A standard property. Defines the mapping between the > child > -MC address space and the parent system address space. > - > -The MC address space is defined by 3 components: > - > - > -Valid values for region type are > - 0x0 - MC portals > - 0x1 - QBMAN portals > - > -- #address-cells > -Value type: > -Definition: Must be 3. (see definition in 'ranges' property) > - > -- #size-cells > -Value type: > -
[PATCH v4] dt-bindings: misc: convert fsl,qoriq-mc from txt to YAML
From: Ionut-robert Aron Convert fsl,qoriq-mc to YAML in order to automate the verification process of dts files. In addition, update MAINTAINERS accordingly and, while at it, add some missing files. Signed-off-by: Ionut-robert Aron [laurentiu.tu...@nxp.com: update MINTAINERS, updates & fixes in schema] Signed-off-by: Laurentiu Tudor --- Changes in v4: - use $ref to point to fsl,qoriq-mc-dpmac binding Changes in v3: - dropped duplicated "fsl,qoriq-mc-dpmac" schema and replaced with reference to it - fixed a dt_binding_check warning Changes in v2: - fixed errors reported by yamllint - dropped multiple unnecessary quotes - used schema instead of text in description - added constraints on dpmac reg property .../devicetree/bindings/misc/fsl,qoriq-mc.txt | 196 -- .../bindings/misc/fsl,qoriq-mc.yaml | 186 + .../ethernet/freescale/dpaa2/overview.rst | 5 +- MAINTAINERS | 4 +- 4 files changed, 193 insertions(+), 198 deletions(-) delete mode 100644 Documentation/devicetree/bindings/misc/fsl,qoriq-mc.txt create mode 100644 Documentation/devicetree/bindings/misc/fsl,qoriq-mc.yaml diff --git a/Documentation/devicetree/bindings/misc/fsl,qoriq-mc.txt b/Documentation/devicetree/bindings/misc/fsl,qoriq-mc.txt deleted file mode 100644 index 7b486d4985dc.. --- a/Documentation/devicetree/bindings/misc/fsl,qoriq-mc.txt +++ /dev/null @@ -1,196 +0,0 @@ -* Freescale Management Complex - -The Freescale Management Complex (fsl-mc) is a hardware resource -manager that manages specialized hardware objects used in -network-oriented packet processing applications. After the fsl-mc -block is enabled, pools of hardware resources are available, such as -queues, buffer pools, I/O interfaces. These resources are building -blocks that can be used to create functional hardware objects/devices -such as network interfaces, crypto accelerator instances, L2 switches, -etc. - -For an overview of the DPAA2 architecture and fsl-mc bus see: -Documentation/networking/device_drivers/ethernet/freescale/dpaa2/overview.rst - -As described in the above overview, all DPAA2 objects in a DPRC share the -same hardware "isolation context" and a 10-bit value called an ICID -(isolation context id) is expressed by the hardware to identify -the requester. - -The generic 'iommus' property is insufficient to describe the relationship -between ICIDs and IOMMUs, so an iommu-map property is used to define -the set of possible ICIDs under a root DPRC and how they map to -an IOMMU. - -For generic IOMMU bindings, see -Documentation/devicetree/bindings/iommu/iommu.txt. - -For arm-smmu binding, see: -Documentation/devicetree/bindings/iommu/arm,smmu.yaml. - -The MSI writes are accompanied by sideband data which is derived from the ICID. -The msi-map property is used to associate the devices with both the ITS -controller and the sideband data which accompanies the writes. - -For generic MSI bindings, see -Documentation/devicetree/bindings/interrupt-controller/msi.txt. - -For GICv3 and GIC ITS bindings, see: -Documentation/devicetree/bindings/interrupt-controller/arm,gic-v3.yaml. - -Required properties: - -- compatible -Value type: -Definition: Must be "fsl,qoriq-mc". A Freescale Management Complex -compatible with this binding must have Block Revision -Registers BRR1 and BRR2 at offset 0x0BF8 and 0x0BFC in -the MC control register region. - -- reg -Value type: -Definition: A standard property. Specifies one or two regions -defining the MC's registers: - - -the first region is the command portal for the -this machine and must always be present - - -the second region is the MC control registers. This -region may not be present in some scenarios, such -as in the device tree presented to a virtual machine. - -- ranges -Value type: -Definition: A standard property. Defines the mapping between the child -MC address space and the parent system address space. - -The MC address space is defined by 3 components: - - -Valid values for region type are - 0x0 - MC portals - 0x1 - QBMAN portals - -- #address-cells -Value type: -Definition: Must be 3. (see definition in 'ranges' property) - -- #size-cells -Value type: -Definition: Must be 1. - -Sub-nodes: - -The fsl-mc node may optionally have dpmac sub-nodes that describe -the relationship between the Ethernet MACs which belong to the MC -and the Ethernet PHYs on the system board. - -The dpmac nodes must be under a node named "dpmacs" which contains -the
