From: Matt Ranostay <mranostay@gmail.com>
To: zonque@gmail.com, dmitry.torokhov@gmail.com
Cc: linux-input@vger.kernel.org, linux-leds@vger.kernel.org,
devicetree@vger.kernel.org, Matt Ranostay <mranostay@gmail.com>
Subject: [PATCH v5 0/2] cap11xx: add LED support
Date: Wed, 17 Jun 2015 20:58:15 -0700 [thread overview]
Message-ID: <1434599897-22505-1-git-send-email-mranostay@gmail.com> (raw)
Changes from v4:
* Update docs to show proper address and size properties for DT bindings
* Make all LEDs blank on startup, and remove racey schedule_work calls
that did this in last revisions
* Disable cap11xx_set_sleep() if any LEDs registered
* TODO: Make cap11xx_set_sleep() able to detect if LEDs are in use and
calculate which power state it should be in.
Matt Ranostay (2):
dt: add cap11xx LED documentation
cap11xx: add LED support
.../devicetree/bindings/input/cap11xx.txt | 25 ++++
drivers/input/keyboard/cap11xx.c | 140 ++++++++++++++++++++-
2 files changed, 162 insertions(+), 3 deletions(-)
--
1.9.1
next reply other threads:[~2015-06-18 3:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 3:58 Matt Ranostay [this message]
2015-06-18 3:58 ` [PATCH v5 1/2] dt: add cap11xx LED documentation Matt Ranostay
2015-06-18 6:49 ` Jacek Anaszewski
2015-06-22 17:59 ` Dmitry Torokhov
2015-06-23 8:36 ` Jacek Anaszewski
[not found] ` <55891A84.1070509-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2015-06-23 17:23 ` Matt Ranostay
2015-06-23 18:07 ` Dmitry Torokhov
2015-06-23 18:24 ` Matt Ranostay
[not found] ` <CAKzfze_n7hf629=aUb6j-tcPcBLcwTH-a8yLJWS0cLM=dOkEVQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-06-23 18:52 ` Dmitry Torokhov
2015-06-24 7:28 ` Jacek Anaszewski
2015-06-24 7:44 ` Jacek Anaszewski
2015-06-18 3:58 ` [PATCH v5 2/2] cap11xx: add LED support Matt Ranostay
2015-06-18 6:51 ` Jacek Anaszewski
2015-06-20 2:32 ` Matt Ranostay
2015-06-22 18:08 ` Dmitry Torokhov
2015-06-23 7:00 ` Jacek Anaszewski
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=1434599897-22505-1-git-send-email-mranostay@gmail.com \
--to=mranostay@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=zonque@gmail.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;
as well as URLs for NNTP newsgroup(s).