[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <72114aa0-3154-2027-0eae-36d08003e436@infradead.org>
Date: Sun, 7 Nov 2021 18:24:54 -0800
From: Randy Dunlap <rdunlap@...radead.org>
To: Ansuel Smith <ansuelsmth@...il.com>, Andrew Lunn <andrew@...n.ch>,
Vivien Didelot <vivien.didelot@...il.com>,
Florian Fainelli <f.fainelli@...il.com>,
Vladimir Oltean <olteanv@...il.com>,
"David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
Jonathan Corbet <corbet@....net>, Pavel Machek <pavel@....cz>,
John Crispin <john@...ozen.org>, netdev@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-doc@...r.kernel.org, linux-leds@...r.kernel.org
Subject: Re: [RFC PATCH v2 3/5] leds: trigger: add offload-phy-activity
trigger
On 11/7/21 4:24 PM, Ansuel Smith wrote:
> diff --git a/drivers/leds/trigger/Kconfig b/drivers/leds/trigger/Kconfig
> index 33aba8defeab..14023e160ba1 100644
> --- a/drivers/leds/trigger/Kconfig
> +++ b/drivers/leds/trigger/Kconfig
> @@ -164,4 +164,33 @@ config LEDS_TRIGGER_TTY
>
> When build as a module this driver will be called ledtrig-tty.
>
> +config LEDS_OFFLOAD_TRIGGER_PHY_ACTIVITY
> + tristate "LED Offload Trigger for PHY Activity"
> + depends on LEDS_OFFLOAD_TRIGGERS
> + help
> + This allows LEDs to be configured to run by hardware and offloaded
to be run
> + based on some rules. The LED will blink or be on based on the PHY
Could "on" be changed to ON or "on" or 'on' here: be ON based on the PHY
> + Activity for example on packet receive or based on the link speed.
--
~Randy
Powered by blists - more mailing lists