public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Samuel Ortiz <sameo@linux.intel.com>
To: Richard Purdie <rpurdie@rpsys.net>
Cc: Pavel Machek <pavel@ucw.cz>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] leds: Add WM831x status LED driver
Date: Wed, 9 Sep 2009 11:12:42 +0200	[thread overview]
Message-ID: <20090909091239.GA4292@sortiz.org> (raw)
In-Reply-To: <1252331484.17852.50.camel@dax.rpnet.com>

Hi Richard,

On Mon, Sep 07, 2009 at 02:51:24PM +0100, Richard Purdie wrote:
> On Mon, 2009-09-07 at 15:22 +0200, Pavel Machek wrote:
> > On Sat 2009-09-05 14:09:21, Mark Brown wrote:
> > > The WM831x devices feature two software controlled status LEDs with
> > > hardware assisted blinking.
> > > 
> > > The device can also autonomously control the LEDs based on a selection
> > > of sources.  This can be configured at boot time using either platform
> > > data or the chip OTP.  A sysfs file in the style of that for triggers
> > > allowing the control source to be configured at run time.  Triggers
> > > can't be used here since they can't depend on the implementation details
> > > of a specific LED type.
> > 
> > I believe people *were* doing that with triggers in other drivers...?
> 
> We did talk about allowing the LED triggers to choose whether they were
> visible to a given LED. At present the mechanism doesn't exist because
> we've never had a user.
> 
> It would just be a case of adding a new optional function to the trigger
> to say whether it supported a given LED or not and calling that function
> from led_trigger_show().
> 
> I've queued this driver but that would be a nice enhancement.
Unless you're basing your tree on linux-next, you may have issues applying
this patch since the wm831x header is not in Linus tree yet.
If you have troubles with this patch, let me know and I'll queue it.

Cheers,
Samuel.


> Cheers,
> 
> Richard
> 
> -- 
> Richard Purdie
> Intel Open Source Technology Centre
> 

-- 
Intel Open Source Technology Centre
http://oss.intel.com/

  reply	other threads:[~2009-09-09  9:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-05 13:09 [PATCH 1/2] backlight: Add WM831x backlight driver Mark Brown
2009-09-05 13:09 ` [PATCH 2/2] leds: Add WM831x status LED driver Mark Brown
2009-09-07  7:25   ` Andrey Panin
2009-09-07  9:07     ` Mark Brown
2009-09-07 13:22   ` Pavel Machek
2009-09-07 13:51     ` Richard Purdie
2009-09-09  9:12       ` Samuel Ortiz [this message]
2009-09-09  9:38         ` Mark Brown
2009-09-09  9:52           ` 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=20090909091239.GA4292@sortiz.org \
    --to=sameo@linux.intel.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=rpurdie@rpsys.net \
    /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