[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YYhUGNs1I0RWriln@Ansuel-xps.localdomain>
Date: Sun, 7 Nov 2021 23:32:56 +0100
From: Ansuel Smith <ansuelsmth@...il.com>
To: Marek BehĂșn <kabel@...nel.org>
Cc: 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 2/6] leds: permit to declare supported offload
triggers
On Sun, Nov 07, 2021 at 11:06:24PM +0100, Marek BehĂșn wrote:
> On Sun, 7 Nov 2021 18:57:14 +0100
> Ansuel Smith <ansuelsmth@...il.com> wrote:
>
> > With LEDs that can be offload driven, permit to declare supported triggers
> > in the dts and add them to the cled struct to be used by the related
> > offload trigger. This is particurally useful for phy that have support
> > for HW blinking on tx/rx traffic or based on the speed link.
> >
> > Signed-off-by: Ansuel Smith <ansuelsmth@...il.com>
>
> NAK. The device-tree shouldn't define this, only the LED's function as
> designated by the manufacturer of the device.
>
> Marek
Sure I will add a way to ask the led driver if the trigger is supported
and report it.
--
Ansuel
Powered by blists - more mailing lists