public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Pavel Machek <pavel@suse.cz>
Cc: Richard Purdie <rpurdie@linux.intel.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] leds: Add WM8350 LED driver
Date: Sat, 15 Nov 2008 17:43:50 +0000	[thread overview]
Message-ID: <20081115174350.GA12466@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20081115172945.GC1523@ucw.cz>

On Sat, Nov 15, 2008 at 06:29:45PM +0100, Pavel Machek wrote:
> On Thu 2008-11-13 12:39:57, Mark Brown wrote:

> > regulators for their hardware and then then use wm8350_register_led() to
> > instantiate the LED driver.

> What kind of hw is this? 1W led attached to some kind of PDA?

Depends on the hardware design - this is a generic component for battery
powered devices (including PDAs).  Typical applications include
relatively high power things like backlights.

  reply	other threads:[~2008-11-15 17:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-13 12:39 [PATCH] leds: Add WM8350 LED driver Mark Brown
2008-11-13 14:57 ` [PATCH] leds: Fix locking for WM8350 Mark Brown
2008-11-15 17:31   ` Pavel Machek
2008-11-15 17:50     ` Mark Brown
2008-11-15 18:51       ` Pavel Machek
2008-11-15 19:14         ` Mark Brown
2008-11-17 15:33           ` Richard Purdie
2008-11-17 23:05             ` Mark Brown
2008-11-18  8:33             ` Pavel Machek
2008-11-14 23:19 ` [PATCH] leds: Add WM8350 LED driver Andrew Morton
2008-11-17 11:57   ` Mark Brown
2008-11-15 17:29 ` Pavel Machek
2008-11-15 17:43   ` Mark Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-11-17 14:52 Mark Brown
2008-11-17 15:25 ` Frederik Deweerdt
2008-11-17 15:29   ` Mark Brown
2008-11-26 13:53 Mark Brown
2008-11-26 17:39 ` Sven Wegener
2008-11-26 18:17   ` Mark Brown
2008-11-26 18:26 Mark Brown

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=20081115174350.GA12466@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=rpurdie@linux.intel.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