linux-kernel - Re: [RFC PATCH 1/3] dt-bindings: net: sparx5: Add sparx5-switch bindings

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20201127170052.GV2073444@lunn.ch>
Date:   Fri, 27 Nov 2020 18:00:52 +0100
From:   Andrew Lunn <andrew@...n.ch>
To:     Steen Hegelund <steen.hegelund@...rochip.com>
Cc:     "David S. Miller" <davem@...emloft.net>,
        Jakub Kicinski <kuba@...nel.org>,
        Rob Herring <robh+dt@...nel.org>,
        Lars Povlsen <lars.povlsen@...rochip.com>,
        Bjarni Jonasson <bjarni.jonasson@...rochip.com>,
        Microchip Linux Driver Support <UNGLinuxDriver@...rochip.com>,
        Alexandre Belloni <alexandre.belloni@...tlin.com>,
        Microsemi List <microsemi@...ts.bootlin.com>,
        netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
        devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [RFC PATCH 1/3] dt-bindings: net: sparx5: Add sparx5-switch
 bindings

> +  reg-names:
> +    minItems: 153
> +    items:
> +      - const: dev2g5_0
> +      - const: dev5g_0
> +      - const: pcs5g_br_0
> +      - const: dev2g5_1
> +      - const: dev5g_1
...
> +      - const: ana_ac
> +      - const: vop

> +    switch: switch@...000000 {
> +      compatible = "microchip,sparx5-switch";
> +      reg = <0x10004000 0x4000>, /* dev2g5_0 */
> +        <0x10008000 0x4000>, /* dev5g_0 */
> +        <0x1000c000 0x4000>, /* pcs5g_br_0 */
> +        <0x10010000 0x4000>, /* dev2g5_1 */
> +        <0x10014000 0x4000>, /* dev5g_1 */

...

> +        <0x11800000 0x100000>, /* ana_l2 */
> +        <0x11900000 0x100000>, /* ana_ac */
> +        <0x11a00000 0x100000>; /* vop */

This is a pretty unusual binding.

Why is it not

reg = <0x10004000 0x1af8000>

and the driver can then break up the memory into its sub ranges?

    Andrew