From: Marek Behun <marek.behun@nic•cz>
To: Andrew Lunn <andrew@lunn•ch>
Cc: linux-leds@vger•kernel.org, "Pavel Machek" <pavel@ucw•cz>,
jacek.anaszewski@gmail•com, "Dan Murphy" <dmurphy@ti•com>,
"Ondřej Jirman" <megous@megous•com>,
netdev@vger•kernel.org, "Russell King" <linux@armlinux•org.uk>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin•com>,
"Gregory Clement" <gregory.clement@bootlin•com>,
linux-kernel@vger•kernel.org
Subject: Re: [PATCH RFC leds + net-next v2 1/1] net: phy: marvell: add support for PHY LEDs via LED class
Date: Thu, 23 Jul 2020 23:46:15 +0200 [thread overview]
Message-ID: <20200723234615.1af24bb0@nic.cz> (raw)
In-Reply-To: <20200723213531.GK1553578@lunn.ch>
On Thu, 23 Jul 2020 23:35:31 +0200
Andrew Lunn <andrew@lunn•ch> wrote:
> I thought the brightness file disappeared when a trigger takes
> over. So is this possible?
>
> Andrew
It does not disappear nor should it. When you have a LED with 10 levels
of brightness, you want to be able to configure with which brightness
it blinks when controlled by a trigger. SW triggers use that brightness
which was stored into the brightness file when blinking the LED.
Marek
next prev parent reply other threads:[~2020-07-23 21:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 18:13 [PATCH RFC leds + net-next v2 0/1] Add support for LEDs on Marvell PHYs Marek Behún
2020-07-23 18:13 ` [PATCH RFC leds + net-next v2 1/1] net: phy: marvell: add support for PHY LEDs via LED class Marek Behún
2020-07-23 21:35 ` Andrew Lunn
2020-07-23 21:44 ` Pavel Machek
2020-07-23 21:46 ` Marek Behun [this message]
2020-07-23 22:53 ` Marek Behun
2020-07-24 10:24 ` Pavel Machek
2020-07-24 13:11 ` Andrew Lunn
2020-07-25 9:41 ` Pavel Machek
2020-07-24 10:29 ` [PATCH RFC leds + net-next v2 0/1] Add support for LEDs on Marvell PHYs Pavel Machek
2020-07-24 13:12 ` Marek Behún
2020-07-24 13:18 ` Marek Behún
2020-07-24 22:38 ` Pavel Machek
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=20200723234615.1af24bb0@nic.cz \
--to=marek.behun@nic$(echo .)cz \
--cc=andrew@lunn$(echo .)ch \
--cc=dmurphy@ti$(echo .)com \
--cc=gregory.clement@bootlin$(echo .)com \
--cc=jacek.anaszewski@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-leds@vger$(echo .)kernel.org \
--cc=linux@armlinux$(echo .)org.uk \
--cc=megous@megous$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pavel@ucw$(echo .)cz \
--cc=thomas.petazzoni@bootlin$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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