From: Rob Herring <robh@kernel.org>
To: Chris Packham <chris.packham@alliedtelesis.co.nz>
Cc: lee@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, tsbogend@alpha.franken.de,
hkallweit1@gmail.com, linux@armlinux.org.uk,
sander@svanheule.net, daniel@makrotopia.org,
markus.stockhausen@gmx.de, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-mips@vger.kernel.org
Subject: Re: [PATCH net-next v6 1/6] dt-bindings: mfd: Add switch to RTL9300
Date: Tue, 4 Feb 2025 10:02:13 -0600 [thread overview]
Message-ID: <20250204160213.GA2811393-robh@kernel.org> (raw)
In-Reply-To: <20250204030249.1965444-2-chris.packham@alliedtelesis.co.nz>
On Tue, Feb 04, 2025 at 04:02:44PM +1300, Chris Packham wrote:
> Add bindings for the ethernet-switch portion of the RTL9300.
>
> Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
> ---
>
> Notes:
> Changes in v6:
> - New
> - I'd like to enforce the property being "ethernet-ports" but I see the
> generic binding allows "ports" as well. Can I just add ethernet-ports:
> type: object here
Yes. And keep 'additionalProperties'.
> or does by driver need to handle both "ports" and
> "ethernet-ports" (I see some do and some don't).
No, it doesn't.
>
> .../bindings/mfd/realtek,rtl9301-switch.yaml | 16 +++++++++++++++-
> 1 file changed, 15 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/mfd/realtek,rtl9301-switch.yaml b/Documentation/devicetree/bindings/mfd/realtek,rtl9301-switch.yaml
> index f053303ab1e6..cb54abda5e6a 100644
> --- a/Documentation/devicetree/bindings/mfd/realtek,rtl9301-switch.yaml
> +++ b/Documentation/devicetree/bindings/mfd/realtek,rtl9301-switch.yaml
> @@ -14,6 +14,8 @@ description:
> number of different peripherals are accessed through a common register block,
> represented here as a syscon node.
>
> +$ref: /schemas/net/ethernet-switch.yaml#
If you don't have any device specific per port properties, then this
needs to be: ethernet-switch.yaml#/$defs/ethernet-ports
> +
> properties:
> compatible:
> items:
> @@ -45,7 +47,7 @@ required:
> - compatible
> - reg
>
> -additionalProperties: false
> +unevaluatedProperties: false
>
> examples:
> - |
> @@ -110,5 +112,17 @@ examples:
> };
> };
> };
> +
> + ethernet-ports {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + port@0 {
> + reg = <0>;
> + };
> + port@1 {
> + reg = <1>;
> + };
> + };
> };
>
> --
> 2.48.1
>
next prev parent reply other threads:[~2025-02-04 16:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 3:02 [PATCH net-next v6 0/6] RTL9300 MDIO driver Chris Packham
2025-02-04 3:02 ` [PATCH net-next v6 1/6] dt-bindings: mfd: Add switch to RTL9300 Chris Packham
2025-02-04 8:09 ` Krzysztof Kozlowski
2025-02-04 20:14 ` Chris Packham
2025-02-04 16:02 ` Rob Herring [this message]
2025-02-04 3:02 ` [PATCH net-next v6 2/6] dt-bindings: net: Add Realtek MDIO controller Chris Packham
2025-02-04 16:03 ` Rob Herring (Arm)
2025-02-04 3:02 ` [PATCH net-next v6 3/6] dt-bindings: mfd: Add MDIO interface to rtl9301-switch Chris Packham
2025-02-04 3:02 ` [PATCH net-next v6 4/6] net: mdio: Add RTL9300 MDIO driver Chris Packham
2025-02-09 14:19 ` Sander Vanheule
2025-02-11 21:06 ` Chris Packham
2025-02-04 3:02 ` [PATCH net-next v6 5/6] mips: dts: realtek: Add MDIO controller Chris Packham
2025-02-04 3:02 ` [PATCH net-next v6 6/6] mips: dts: cameo-rtl9302c: Add switch block Chris Packham
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250204160213.GA2811393-robh@kernel.org \
--to=robh@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=conor+dt@kernel.org \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=markus.stockhausen@gmx.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sander@svanheule.net \
--cc=tsbogend@alpha.franken.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).