From: Matt Ranostay <mranostay@gmail.com>
To: dmitry.torokhov@gmail.com
Cc: linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
linux-input@vger.kernel.org, Matt Ranostay <mranostay@gmail.com>
Subject: [PATCH RESEND 0/2] cap11xx: add LED support
Date: Tue, 4 Aug 2015 21:24:54 -0700 [thread overview]
Message-ID: <1438748696-28452-1-git-send-email-mranostay@gmail.com> (raw)
Several cap11xx variants have LEDs that be can be controlled, and this
patchset implements this functionality
Matt Ranostay (2):
dt: add cap11xx LED documentation
cap11xx: add LED support
.../devicetree/bindings/input/cap11xx.txt | 19 +++
drivers/input/keyboard/cap11xx.c | 140 ++++++++++++++++++++-
2 files changed, 156 insertions(+), 3 deletions(-)
--
1.9.1
next reply other threads:[~2015-08-05 4:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 4:24 Matt Ranostay [this message]
2015-08-05 4:24 ` [PATCH RESEND 1/2] dt: add cap11xx LED documentation Matt Ranostay
2015-08-05 4:24 ` [PATCH RESEND 2/2] cap11xx: add LED support Matt Ranostay
2015-08-17 6:22 ` Dmitry Torokhov
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=1438748696-28452-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 \
/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).