From: leo60228 <leo@60228.dev>
To: "Enrico Weigelt, metux IT consult" <lkml@metux.net>,
hdegoede@redhat.com, platform-driver-x86@vger.kernel.org,
linux-leds@vger.kernel.org
Subject: Re: [PATCH v2] platform/x86: add support for Acer Predator LEDs
Date: Wed, 16 Jun 2021 11:56:31 -0400 [thread overview]
Message-ID: <ae4e7db3-ffc5-b8f3-c08c-bba6882d44ad@60228.dev> (raw)
In-Reply-To: <87e6f17f-3d82-ac63-b5eb-e7f3205f59e8@metux.net>
> Can you please tell a bit more what these LEDs are actually used for ?
> Do they have some names or symbols ? Are they also controlled by
> something else (e.g. numlock or shiftlock leds)
They're used for the keyboard backlight. This functionality is pretty
common on gaming laptops.
next prev parent reply other threads:[~2021-06-16 15:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 22:19 [PATCH] platform/x86: add support for Acer Predator LEDs leo60228
2021-06-15 23:24 ` Barnabás Pőcze
[not found] ` <CAPRrO0xZunTfYYSOg-Gvk18FMHPufAURZ=fWjQN1bmP=RuuzGA@mail.gmail.com>
2021-06-16 0:21 ` Barnabás Pőcze
2021-06-16 0:24 ` leo60228
2021-06-16 0:51 ` [PATCH v2] " leo60228
2021-06-16 15:43 ` Enrico Weigelt, metux IT consult
2021-06-16 15:56 ` leo60228 [this message]
2021-06-16 17:20 ` Enrico Weigelt, metux IT consult
2021-06-16 17:50 ` Hans de Goede
2021-06-21 19:23 ` Enrico Weigelt, metux IT consult
2021-06-21 19:43 ` Hans de Goede
2021-06-22 10:19 ` input devices vs. keyboard backlights [WAS: [PATCH v2] platform/x86: add support for Acer Predator LEDs] Enrico Weigelt, metux IT consult
2021-06-22 10:46 ` Hans de Goede
2021-06-16 15:41 ` [PATCH] platform/x86: add support for Acer Predator LEDs Enrico Weigelt, metux IT consult
2021-06-16 16:06 ` leo60228
2021-06-16 17:22 ` Enrico Weigelt, metux IT consult
2021-06-16 16:00 ` Hans de Goede
2021-06-16 16:16 ` leo60228
2021-06-16 16:39 ` Hans de Goede
2021-06-16 17:01 ` leo60228
2021-06-16 17:13 ` Jafar Akhondali
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=ae4e7db3-ffc5-b8f3-c08c-bba6882d44ad@60228.dev \
--to=leo@60228.dev \
--cc=hdegoede@redhat.com \
--cc=linux-leds@vger.kernel.org \
--cc=lkml@metux.net \
--cc=platform-driver-x86@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