From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Adam Goode <agoode@google.com>
Cc: Henrique de Moraes Holschuh <ibm-acpi@hmh.eng.br>,
Darren Hart <dvhart@infradead.org>,
ibm-acpi-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org
Subject: Re: [ibm-acpi-devel] [PATCH 1/1] thinkpad_acpi: Add support for status (external cover) LED
Date: Tue, 7 Feb 2017 23:01:32 -0200 [thread overview]
Message-ID: <20170208010132.GB7028@khazad-dum.debian.net> (raw)
In-Reply-To: <CAOf41Nka4UNk_XUegEXAOHE-Xf0eOs71fuZgBKr0PHEL9sGyag@mail.gmail.com>
Hello Adam,
I apologise for the delay on answering you.
On Tue, 31 Jan 2017, Adam Goode wrote:
> On Thu, Jan 19, 2017 at 12:21 PM, Adam Goode <agoode@google.com> wrote:
> > This allows the control of the red status LED, which is the dot of the "i"
> > in the word "ThinkPad" on the outside cover of newer models.
> >
> > In the manual, both this LED and the power LED are referred to as
> > the "system-status indicators" without distinction between the two, so
> > I chose "status" as the LED name.
I seem to recall this LED had an ACPI interface that was specific for
it, and allowed it to on/off/sine-wave?
> > Signed-off-by: Adam Goode <agoode@google.com>
> >
> > diff --git a/drivers/platform/x86/thinkpad_acpi.c b/drivers/platform/x86/
> > thinkpad_acpi.c
> > index cacb43fb1df7..6577bf8e5635 100644
> > --- a/drivers/platform/x86/thinkpad_acpi.c
> > +++ b/drivers/platform/x86/thinkpad_acpi.c
> > @@ -5611,11 +5611,11 @@ static const char * const
> > tpacpi_led_names[TPACPI_LED_NUMLEDS] = {
> > "tpacpi::standby",
> > "tpacpi::dock_status1",
> > "tpacpi::dock_status2",
> > - "tpacpi::unknown_led2",
> > + "tpacpi::status",
> > "tpacpi::unknown_led3",
> > "tpacpi::thinkvantage",
> > };
> > -#define TPACPI_SAFE_LEDS 0x1081U
> > +#define TPACPI_SAFE_LEDS 0x1481U
What happens on older Lenovo models (x00, x10, x20 series?)? I think
the T410 already had it...
Also, please add code to not export it to userspace (as a led class) on
IBM.
--
Henrique Holschuh
next prev parent reply other threads:[~2017-02-08 1:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 17:21 Adam Goode
[not found] ` <CAOf41Nka4UNk_XUegEXAOHE-Xf0eOs71fuZgBKr0PHEL9sGyag@mail.gmail.com>
2017-02-08 1:01 ` Henrique de Moraes Holschuh [this message]
2017-02-12 18:22 ` [ibm-acpi-devel] " Sebastian Reichel
2017-02-12 18:27 ` Adam Goode
2017-05-07 16:38 ` Pavel Machek
2017-05-07 23:49 ` Henrique de Moraes Holschuh
2017-05-12 10:43 ` Pavel Machek
2017-05-12 17:23 ` [ibm-acpi-devel] " Henrique de Moraes Holschuh
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=20170208010132.GB7028@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=agoode@google.com \
--cc=dvhart@infradead.org \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=ibm-acpi@hmh.eng.br \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®