From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Linus Walleij <linus.walleij@stericsson.com>
Cc: Richard Purdie <rpurdie@rpsys.net>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Samuel Ortiz <sameo@linux.intel.com>,
Shreshtha Kumar Sahu <shreshthakumar.sahu@stericsson.com>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH] leds: driver for ab5500 high voltage leds
Date: Sat, 3 Dec 2011 21:49:26 +0000 [thread overview]
Message-ID: <20111203214924.GA21511@sirena.org.uk> (raw)
In-Reply-To: <1322834182-26168-1-git-send-email-linus.walleij@stericsson.com>
On Fri, Dec 02, 2011 at 02:56:22PM +0100, Linus Walleij wrote:
> +What: /sys/class/leds/<led>/led_current
> +Date: December 2011
> +KernelVersion: 3.3
> +Contact: Shreshtha Kumar SAHU <shreshthakumar.sahu@stericsson.com>
> +Description:
> + Read and set the current limit for the LED. Value in
> + milliampere.
This sounds like a platform data thing - normally if you get a current
limit wrong you're heading for magic smoke so it's not something you
want to be playing with at runtime from userspace.
next prev parent reply other threads:[~2011-12-03 21:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-02 13:56 Linus Walleij
2011-12-03 21:49 ` Mark Brown [this message]
2011-12-07 14:16 ` Linus Walleij
2011-12-07 15:47 ` Mark Brown
2011-12-03 22:49 ` Denis Kuzmenko
2011-12-07 14:07 ` Linus Walleij
2011-12-07 18:01 ` Denis Kuzmenko
2011-12-08 0:00 ` Andrew Morton
2011-12-08 1:19 ` Mark Brown
2011-12-14 10:23 ` Shreshtha Kumar SAHU
2011-12-14 11:37 ` Mark Brown
2011-12-14 14:01 ` Shreshtha Kumar SAHU
2011-12-14 14:47 ` Mark Brown
2011-12-14 18:34 ` Linus Walleij
2011-12-15 7:11 ` Mark Brown
2011-12-16 5:10 ` Shreshtha Kumar SAHU
2011-12-22 17:43 ` Mark Brown
2011-12-19 11:26 ` Samuel Ortiz
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=20111203214924.GA21511@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=akpm@linux-foundation.org \
--cc=linus.walleij@linaro.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rpurdie@rpsys.net \
--cc=sameo@linux.intel.com \
--cc=shreshthakumar.sahu@stericsson.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®