Linux LED subsystem development
 help / color / mirror / Atom feed
From: Evan McClain <aeroevan@gmail.com>
To: linux-leds@vger.kernel.org
Subject: Chromebook Keyboard LEDs
Date: Sat, 02 Jan 2016 16:54:02 -0500	[thread overview]
Message-ID: <1451771642.25561.10.camel@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1549 bytes --]

Hi list,

I'm not sure how kosher it is to submit changes that I didn't author
(cherry-picks from the chromium kernel), but since these patches are a
few years old and having support in the mainline kernel would be nice I
thought I'd give it a shot.

I have tested on my Chromebook Pixel 2 (samus) which runs fine but is
missing a few drivers (this and ASoC, but ASoC isn't as easy).


The following changes since commit
376886d44f4cba72c4942aa1ac834ba00f6f222d:

  leds: bcm6358: remove unneeded busy status check (2015-12-17 09:39:02
+0100)

are available in the git repository at:

  https://github.com/aeroevan/linux.git for-leds

for you to fetch changes up to
589e241e11fa01a5fef59b40c9ad826e11322e4f:

  leds-chromeos-keyboard: Add ACPI _HID probing (2016-01-01 02:04:09
-0500)

----------------------------------------------------------------
Duncan Laurie (1):
      leds-chromeos-keyboard: Add ACPI _HID probing

Simon Que (3):
      leds: Add Chrome OS keyboard LEDs driver
      leds: chromeos keyboard name should contain "kbd_backlight"
      leds: Fix chromeos keyboard LED suspend behavior

 drivers/leds/Kconfig                  |   7 ++
 drivers/leds/Makefile                 |   1 +
 drivers/leds/leds-chromeos-keyboard.c | 127
++++++++++++++++++++++++++++++++++
 3 files changed, 135 insertions(+)
 create mode 100644 drivers/leds/leds-chromeos-keyboard.c

Thanks
-- 
Evan McClain
https://keybase.io/aeroevan

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

             reply	other threads:[~2016-01-02 21:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-02 21:54 Evan McClain [this message]
2016-01-04  9:24 ` Chromebook Keyboard LEDs 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=1451771642.25561.10.camel@gmail.com \
    --to=aeroevan@gmail.com \
    --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