Subject: Re: [PATCH v2] dt-bindings: leds: Document "netdev" trigger

From: Lee Jones <[email-masked]>
Date: Thu, 25 Jul 2024 09:50:42 +0100

Cc: Andrew and netdev

On Mon, 08 Jul 2024, Marek Vasut wrote:

> Document the "netdev" trigger which is used to control LEDs by
> network device activity. This is an existing trigger used in
> existing DTs, document it so validation of those DTs would pass.
> 
> Signed-off-by: Marek Vasut <[email-masked]>
> ---
> Cc: Conor Dooley <[email-masked]>
> Cc: Jacek Anaszewski <[email-masked]>
> Cc: Krzysztof Kozlowski <[email-masked]>
> Cc: Lee Jones <[email-masked]>
> Cc: Pavel Machek <[email-masked]>
> Cc: Rob Herring <[email-masked]>
> Cc: [email-masked]
> Cc: [email-masked]
> ---
> V2: Expand the commit message slightly
> ---
>  Documentation/devicetree/bindings/leds/common.yaml | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/leds/common.yaml b/Documentation/devicetree/bindings/leds/common.yaml
> index 8a3c2398b10ce..bf9a101e4d420 100644
> --- a/Documentation/devicetree/bindings/leds/common.yaml
> +++ b/Documentation/devicetree/bindings/leds/common.yaml
> @@ -113,6 +113,8 @@ properties:
>              # LED indicates NAND memory activity (deprecated),
>              # in new implementations use "mtd"
>            - nand-disk
> +            # LED indicates network activity
> +          - netdev

netdev is the description of the network development ML/repo, right?

Seems like an odd name for an OS agnostic property?

>              # No trigger assigned to the LED. This is the default mode
>              # if trigger is absent
>            - none
> -- 
> 2.43.0
> 

-- 
Lee Jones [李琼斯]