From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: "小龙 陈" <chillermillerlong@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: thinkpad_acpi does not generate correct ACPI events when brightness_enable=0
Date: Sat, 19 Nov 2011 13:44:23 -0200 [thread overview]
Message-ID: <20111119154423.GA11743@khazad-dum.debian.net> (raw)
In-Reply-To: <BAY156-W333AEB3C478890404DB815A3C50@phx.gbl>
On Sat, 19 Nov 2011, 小龙 陈 wrote:
> rmmod thinkpad_acpi modprobe thinkpad_acpi brightness_enable=0
> The "acpi_listen" command shows this following when either the brightness up orbrightness down button is pressed:
> ibm/hotkey LEN0068:00 00000080 00006050
This is an auxiliary event, only available in certain Lenovo boxes, and
thinkpad-acpi doesn't do much with it.
> and also the following when the brightness up button is pressed:
> video/brightnessup BRTUP 00000086 00000000
> The following brightness down ACPI event is only generated after the module isreloaded:
> video/brightnessdown BRTDN 00000087 00000000
> Is this a known bug (or even a bug at all)? The kernel bugzilla is down.
It is probably a bug, yes. But where? You're looking at acpi video output,
not thinkpad-acpi output. The ACPI firmware clearly is changing its
behaviour when thinkpad-acpi is reloaded, which probably means it is broken
and it will have to be worked around if a BIOS update doesn't fix it. That
wouldn't be surprising at all...
Are you using the latest BIOS/EC firmware for your thinkpad?
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
prev parent reply other threads:[~2011-11-19 15:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-19 7:14 小龙 陈
2011-11-19 15:44 ` Henrique de Moraes Holschuh [this message]
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=20111119154423.GA11743@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=chillermillerlong@hotmail.com \
--cc=linux-kernel@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®