Re: [PATCH v2 05/19] dt-bindings: arm: microchip: move SparX-5 to generic Microchip binding

Robert Marko
2025-12-16T17:01:15Z

On Tue, Dec 16, 2025 at 4:58 PM Krzysztof Kozlowski <krzk@kernel.org> wrote:
>
> On 15/12/2025 17:35, Robert Marko wrote:
> > Now that we have a generic Microchip binding, lets move SparX-5 as well as
> > there is no reason to have specific binding file for each SoC series.
> >
> > The check for AXI node was dropped.
>
> Why?

According to Conor, it is pointless [1]

[1] https://patchwork.kernel.org/project/linux-arm-kernel/patch/20251203122313.1287950-2-robert.marko@sartura.hr/#26691879

Regards,
Robert

>
> >
> > Signed-off-by: Robert Marko <robert.marko@sartura.hr>
> > ---
> > .../bindings/arm/microchip,sparx5.yaml | 67 -------------------
> > .../devicetree/bindings/arm/microchip.yaml | 22 ++++++
> > 2 files changed, 22 insertions(+), 67 deletions(-)
> > delete mode 100644 Documentation/devicetree/bindings/arm/microchip,sparx5.yaml
> >
> > diff --git a/Documentation/devicetree/bindings/arm/microchip,sparx5.yaml b/Documentation/devicetree/bindings/arm/microchip,sparx5.yaml
> > deleted file mode 100644
> > index 9a0d54e9799c..000000000000
> > --- a/Documentation/devicetree/bindings/arm/microchip,sparx5.yaml
> > +++ /dev/null
> > @@ -1,67 +0,0 @@
> > -# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > -%YAML 1.2
> > ----
> > -$id: http://devicetree.org/schemas/arm/microchip,sparx5.yaml#
> > -$schema: http://devicetree.org/meta-schemas/core.yaml#
> > -
> > -title: Microchip Sparx5 Boards
> > -
> > -maintainers:
> > - - Lars Povlsen <lars.povlsen@microchip.com>
> > -
> > -description: |+
> > - The Microchip Sparx5 SoC is a ARMv8-based used in a family of
> > - gigabit TSN-capable gigabit switches.
> > -
> > - The SparX-5 Ethernet switch family provides a rich set of switching
> > - features such as advanced TCAM-based VLAN and QoS processing
> > - enabling delivery of differentiated services, and security through
> > - TCAM-based frame processing using versatile content aware processor
> > - (VCAP)
> > -
> > -properties:
> > - $nodename:
> > - const: '/'
> > - compatible:
> > - oneOf:
> > - - description: The Sparx5 pcb125 board is a modular board,
> > - which has both spi-nor and eMMC storage. The modular design
> > - allows for connection of different network ports.
> > - items:
> > - - const: microchip,sparx5-pcb125
> > - - const: microchip,sparx5
> > -
> > - - description: The Sparx5 pcb134 is a pizzabox form factor
> > - gigabit switch with 20 SFP ports. It features spi-nor and
> > - either spi-nand or eMMC storage (mount option).
> > - items:
> > - - const: microchip,sparx5-pcb134
> > - - const: microchip,sparx5
> > -
> > - - description: The Sparx5 pcb135 is a pizzabox form factor
> > - gigabit switch with 48+4 Cu ports. It features spi-nor and
> > - either spi-nand or eMMC storage (mount option).
> > - items:
> > - - const: microchip,sparx5-pcb135
> > - - const: microchip,sparx5
> > -
> > - axi@600000000:
> > - type: object
> > - description: the root node in the Sparx5 platforms must contain
> > - an axi bus child node. They are always at physical address
> > - 0x600000000 in all the Sparx5 variants.
> > - properties:
> > - compatible:
> > - items:
> > - - const: simple-bus
> > -
> > - required:
> > - - compatible
> > -
> > -required:
> > - - compatible
> > - - axi@600000000
>
> Nothing explains the rationale for doing this.
>
> Best regards,
> Krzysztof

--
Robert Marko
Staff Embedded Linux Engineer
Sartura d.d.
Lendavska ulica 16a
10000 Zagreb, Croatia
Email: robert.marko@sartura.hr
Web: www.sartura.hr