Netdev List
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Ross Cawston <ross@r-sc.ca>
Cc: lee@kernel.org, pavel@kernel.org, robh@kernel.org,
	krzk+dt@kernel.org,  conor+dt@kernel.org,
	chris.packham@alliedtelesis.co.nz, andrew+netdev@lunn.ch,
	 davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
	pabeni@redhat.com,  linux-leds@vger.kernel.org,
	devicetree@vger.kernel.org, netdev@vger.kernel.org,
	 linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] dt-bindings: net: realtek,rtl9301-switch: add port LED controller
Date: Tue, 20 Oct 2026 09:29:06 +0200	[thread overview]
Message-ID: <20261020-weightless-tidy-goshawk-aefb1e@quoll> (raw)
In-Reply-To: <20261018194339.132-3-ross@r-sc.ca>

On Sun, Oct 18, 2026 at 12:43:37PM -0700, Ross Cawston wrote:
> The switch drives the port LEDs, and some boards wire LEDs to it that
> have no hardware function and are switched in software, such as PoE
> status LEDs. Allow the software LED control block, described by
> realtek,rtl9301-port-leds, as a child of the switch like its I2C and
> MDIO controllers.
> 
> Signed-off-by: Ross Cawston <ross@r-sc.ca>
> ---
>  .../devicetree/bindings/net/realtek,rtl9301-switch.yaml        | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/net/realtek,rtl9301-switch.yaml b/Documentation/devicetree/bindings/net/realtek,rtl9301-switch.yaml
> index 80eabc17066..9529327ee0c 100644
> --- a/Documentation/devicetree/bindings/net/realtek,rtl9301-switch.yaml
> +++ b/Documentation/devicetree/bindings/net/realtek,rtl9301-switch.yaml
> @@ -57,6 +57,9 @@ patternProperties:
>    'mdio-controller@[0-9a-f]+$':
>      $ref: realtek,rtl9301-mdio.yaml#
>  
> +  'led-controller@[0-9a-f]+$':
> +    $ref: /schemas/leds/realtek,rtl9301-port-leds.yaml#

This depends on previous patch, so cover letter should be explicit what
maintainers can or cannot do with it.

Best regards,
Krzysztof


  reply	other threads:[~2026-10-20  7:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-18 19:43 [PATCH 0/3] leds: add Realtek RTL9300 port LEDs under software control Ross Cawston
2026-10-18 19:43 ` [PATCH 1/3] dt-bindings: leds: add Realtek RTL9301 port LEDs Ross Cawston
2026-10-18 19:43 ` [PATCH 2/3] dt-bindings: net: realtek,rtl9301-switch: add port LED controller Ross Cawston
2026-10-20  7:29   ` Krzysztof Kozlowski [this message]
2026-10-18 19:43 ` [PATCH 3/3] leds: add Realtek RTL9300 port LED driver Ross Cawston
2026-10-19  7:01   ` Uwe Kleine-König
2026-10-18 22:36 ` [PATCH 0/3] leds: add Realtek RTL9300 port LEDs under software control Andrew Lunn
2026-10-18 23:20   ` Ross Cawston
2026-10-19  0:02     ` Andrew Lunn
2026-10-19  5:42       ` Ross Cawston
2026-10-19  6:41         ` AW: " Markus Stockhausen
2026-10-19 23:00           ` Ross Cawston

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=20261020-weightless-tidy-goshawk-aefb1e@quoll \
    --to=krzk@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=chris.packham@alliedtelesis.co.nz \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=kuba@kernel.org \
    --cc=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pavel@kernel.org \
    --cc=robh@kernel.org \
    --cc=ross@r-sc.ca \
    /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