public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: linux-acpi@vger.kernel.org, Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>
Subject: brightness control on thinkpad t61p
Date: Sun, 23 Dec 2007 00:00:57 -0800	[thread overview]
Message-ID: <20071223000057.739d5891.akpm@linux-foundation.org> (raw)


When I fire up the latest Linus tree on my thinkpad t61p I get:

thinkpad_acpi: ThinkPad ACPI Extras v0.17
thinkpad_acpi: http://ibm-acpi.sf.net/
thinkpad_acpi: ThinkPad BIOS 7LET44WW (1.14 ), EC 7KHT22WW-1.06
thinkpad_acpi: Lenovo ThinkPad T61p
thinkpad_acpi: radio switch found; radios are enabled
ACPI: Lid Switch [LID]
input: Sleep Button (CM) as /class/input/input6
ACPI: Sleep Button (CM) [SLPB]
thinkpad_acpi: standard ACPI backlight interface available, not loading native one...



and /sys/class/backlight/thinkpad_screen/brightness is no longer present, so
my `brightness' script no longer works.  That, my friends, is a regression.

Here's my script:

(
0 sh -c "echo $1 > /proc/acpi/sony/brightness"
0 sh -c "echo $1 > /proc/acpi/sony/brightness_default"
0 sh -c "echo $1 > /sys/class/backlight/sony/brightness"
0 sh -c "echo $1 > /sys/class/backlight/thinkpad_screen/brightness"
) 2>/dev/null

which rather shows how pathetic we are in this area.  Ho hum.


So I go hunting around and find

	/sys/class/backlight/acpi_video0/
and
	/sys/class/backlight/acpi_video1/

Why are there two of them?


Both of these have a `brightness' entry which has contents of 100.  When I set
that to 10, the screen's brightness is not reduced.

So as far as I can tell, we have lost the ability to alter the brightness of
the screen on this machine.



             reply	other threads:[~2007-12-23  8:01 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-23  8:00 Andrew Morton [this message]
2007-12-23 12:16 ` brightness control on thinkpad t61p Rafael J. Wysocki
2007-12-24  7:34 ` Matthew Garrett
2007-12-24 17:14   ` Henrique de Moraes Holschuh
2007-12-26 22:10   ` Andrew Morton
2007-12-26 22:23     ` Matthew Garrett
2007-12-27 12:33       ` Henrique de Moraes Holschuh
2008-01-07  1:36         ` Henrique de Moraes Holschuh
2008-01-07 19:48           ` Matthew Garrett
2008-01-08  0:32             ` Henrique de Moraes Holschuh
2008-01-08  0:45               ` Matthew Garrett
2008-01-08 12:06                 ` Henrique de Moraes Holschuh
2008-01-08 12:18                   ` Matthew Garrett
2008-01-08 12:48                     ` Henrique de Moraes Holschuh
2008-01-08 15:17                       ` Matthew Garrett
2008-01-08 15:45                       ` Richard Purdie
2008-01-08 15:54                         ` Matthew Garrett
2008-01-08 16:29                           ` Richard Purdie
2008-01-08 16:49                             ` Henrique de Moraes Holschuh
2008-01-08 16:56                               ` Richard Purdie
2008-01-08 17:36                                 ` Henrique de Moraes Holschuh
2007-12-27 12:31     ` Henrique de Moraes Holschuh
2007-12-24 17:08 ` Henrique de Moraes Holschuh
2007-12-26 22:10   ` Andrew Morton
2007-12-27 13:15     ` 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=20071223000057.739d5891.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=hmh@hmh.eng.br \
    --cc=linux-acpi@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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