mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: Felipe Balbi <felipe.balbi@nokia.com>
Cc: linux-kernel@vger.kernel.org,
	David Brownell <dbrownell@users.sourceforge.net>,
	Andrew Morton <akpm@linux-foundation.org>,
	Felipe Balbi <me@felipe.balbi.com>,
	Felipe Balbi <me@felipebalbi.com>
Subject: Re: [PATCH] leds: triggers: introduce gpio led trigger
Date: Tue, 17 Feb 2009 23:11:13 +0000	[thread overview]
Message-ID: <1234912273.5312.71.camel@dax.rpnet.com> (raw)
In-Reply-To: <1234869491-29630-2-git-send-email-felipe.balbi@nokia.com>

On Tue, 2009-02-17 at 13:18 +0200, Felipe Balbi wrote:
> From: Felipe Balbi <me@felipe.balbi.com>
> 
> The gpio led trigger will allow leds to be triggered by
> gpio events.
> 
> When we give the led a gpio number, the trigger will
> request_irq() on that so we don't have to keep polling
> for gpio state.
> 
> It's useful for usecases as n810's keypad leds that could
> be triggered by the gpio event generated when user slides
> up to show the keypad.
> 
> We also provide means for userland to tell us what is the
> desired brightness for that special led when it goes on
> so userland could use information from ambient light sensors
> and not set led brightness too high if it's not necessary.
> 
> This trigger was tested with n810.

Added to the LED tree, thanks.

Richard


-- 
Richard Purdie
Intel Open Source Technology Centre


  reply	other threads:[~2009-02-17 23:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-16 12:17 Felipe Balbi
2009-02-16 12:57 ` Felipe Balbi
2009-02-16 13:14   ` Felipe Balbi
2009-02-17 11:18     ` Felipe Balbi
2009-02-17 11:18       ` [PATCH] leds: triggers: introduce gpio led trigger Felipe Balbi
2009-02-17 23:11         ` Richard Purdie [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-02-16 12:12 Felipe Balbi
2009-02-16 12:17 ` Felipe Balbi

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=1234912273.5312.71.camel@dax.rpnet.com \
    --to=rpurdie@rpsys.net \
    --cc=akpm@linux-foundation.org \
    --cc=dbrownell@users.sourceforge.net \
    --cc=felipe.balbi@nokia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=me@felipe.balbi.com \
    --cc=me@felipebalbi.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®