From: Christian Marangi <ansuelsmth@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Marek Vasut <marex@denx.de>,
linux-leds@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
Heiner Kallweit <hkallweit1@gmail.com>,
Jacek Anaszewski <jacek.anaszewski@gmail.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Lee Jones <lee@kernel.org>, Lukasz Majewski <lukma@denx.de>,
Pavel Machek <pavel@ucw.cz>, Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: leds: Document netdev trigger netdev-trigger-mode property
Date: Fri, 17 Jan 2025 17:00:37 +0100 [thread overview]
Message-ID: <678a7ea8.df0a0220.126ab6.dd54@mx.google.com> (raw)
In-Reply-To: <ad334b1b-a4e5-426d-a801-3e1d72455304@lunn.ch>
On Thu, Jan 16, 2025 at 02:32:13PM +0100, Andrew Lunn wrote:
> On Mon, Jan 13, 2025 at 01:23:37AM +0100, Marek Vasut wrote:
> > Document netdev trigger specific netdev-trigger-mode property which
> > is used to configure the netdev trigger mode flags. Those mode flags
> > define events on which the LED acts upon when the hardware offload is
> > enabled. This is traditionally configured via sysfs, but that depends
> > on udev rules which are available either too late or never in case of
> > non-Linux systems.
> >
> > For each LED with linux,default-trigger = "netdev" described in DT, this
> > optional netdev-trigger-mode property supplies the default configuration
> > of the PHY LED mode via DT. This property should be set to a subset of
> > TRIGGER_NETDEV_* flags.
> >
> > Signed-off-by: Marek Vasut <marex@denx.de>
> > ---
> > Cc: Andrew Lunn <andrew@lunn.ch>
> > Cc: Christian Marangi <ansuelsmth@gmail.com>
> > Cc: Conor Dooley <conor+dt@kernel.org>
> > Cc: Heiner Kallweit <hkallweit1@gmail.com>
> > Cc: Jacek Anaszewski <jacek.anaszewski@gmail.com>
> > Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>
> > Cc: Lee Jones <lee@kernel.org>
> > Cc: Lukasz Majewski <lukma@denx.de>
> > Cc: Pavel Machek <pavel@ucw.cz>
> > Cc: Rob Herring <robh@kernel.org>
> > Cc: devicetree@vger.kernel.org
> > Cc: linux-leds@vger.kernel.org
> > ---
> > Documentation/devicetree/bindings/leds/common.yaml | 6 ++++++
> > 1 file changed, 6 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/leds/common.yaml b/Documentation/devicetree/bindings/leds/common.yaml
> > index 3e8319e443392..1f1148fdf20c0 100644
> > --- a/Documentation/devicetree/bindings/leds/common.yaml
> > +++ b/Documentation/devicetree/bindings/leds/common.yaml
> > @@ -233,6 +233,12 @@ properties:
> > Maximum timeout in microseconds after which the flash LED is turned off.
> > Required for flash LED nodes with configurable timeout.
> >
> > + # Requires netdev trigger
> > + netdev-trigger-mode:
> > + description:
> > + The netdev LED trigger default mode flags, use TRIGGER_NETDEV_ * flags.
> > + $ref: /schemas/types.yaml#/definitions/uint32-array
> > +
> > allOf:
> > - if:
> > required:
> > --
>
> An example would be good.
>
> In order to be able to use TRIGGER_NETDEV_* i assume you are doing an
> include which is outside of the usual dt-bindings directory. I don't
> know of the DT Maintainers opinion on that.
>
Well I think we can just move those include to dt-bindings or at worst
define new one (maybe less driver specific) and reference the internal
one... Should not be a problem in theory.
--
Ansuel
next prev parent reply other threads:[~2025-01-17 16:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-13 0:23 [PATCH 1/2] dt-bindings: leds: Document netdev trigger netdev-trigger-mode property Marek Vasut
2025-01-13 0:23 ` [PATCH 2/2] leds: trigger: netdev: Introduce OF mode configuration using " Marek Vasut
2025-01-16 13:47 ` Andrew Lunn
2025-01-21 11:27 ` Marek Vasut
2025-08-07 21:41 ` Heiko Stübner
2025-01-16 13:32 ` [PATCH 1/2] dt-bindings: leds: Document netdev trigger " Andrew Lunn
2025-01-17 16:00 ` Christian Marangi [this message]
2025-01-21 0:00 ` Marek Vasut
2025-01-21 11:37 ` Marek Vasut
2025-08-07 10:09 ` Heiko Stübner
2025-08-09 16:29 ` Andrew Lunn
2025-08-09 19:58 ` Marek Vasut
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=678a7ea8.df0a0220.126ab6.dd54@mx.google.com \
--to=ansuelsmth@gmail.com \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hkallweit1@gmail.com \
--cc=jacek.anaszewski@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=lukma@denx.de \
--cc=marex@denx.de \
--cc=pavel@ucw.cz \
--cc=robh@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.