From: Len Brown <lenb@kernel.org>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [PATCH] Rationalise ACPI backlight implementation
Date: Thu, 24 Jan 2008 16:44:48 -0500 [thread overview]
Message-ID: <200801241644.49114.lenb@kernel.org> (raw)
In-Reply-To: <20071226020325.GA21099@srcf.ucam.org>
On Tuesday 25 December 2007 21:03, Matthew Garrett wrote:
> The sysfs backlight class provides no mechanism for querying the
> acceptable brightness for a backlight. The ACPI spec states that values
> are only valid if they are reported as available by the firmware. Since
> we can't provide that information to userspace, instead collapse the
> range to the number of actual values that can be set.
>
> Signed-off-by: Matthew Garrett <mjg59@srcf.ucam.org>
I wish we did this in the first place.
But doing it now is an API change -- since
with the old way 100 always meant 100% brightness, yes?
so my concern is that if we change what "10" means, somebody like akpm
with an existing script gets grumpy.
-Len
> ---
>
> diff --git a/drivers/acpi/video.c b/drivers/acpi/video.c
> index 521645e..12b2adb 100644
> --- a/drivers/acpi/video.c
> +++ b/drivers/acpi/video.c
> @@ -296,18 +296,26 @@ static int acpi_video_device_set_state(struct acpi_video_device *device, int sta
> static int acpi_video_get_brightness(struct backlight_device *bd)
> {
> unsigned long cur_level;
> + int i;
> struct acpi_video_device *vd =
> (struct acpi_video_device *)bl_get_data(bd);
> acpi_video_device_lcd_get_level_current(vd, &cur_level);
> - return (int) cur_level;
> + for (i=2; i<vd->brightness->count; i++) {
> + if (vd->brightness->levels[i] == cur_level)
> + /* The first two entries are special - see page 575
> + of the ACPI spec 3.0 */
> + return i-2;
> + }
> + return 0;
> }
>
> static int acpi_video_set_brightness(struct backlight_device *bd)
> {
> - int request_level = bd->props.brightness;
> + int request_level = bd->props.brightness+2;
> struct acpi_video_device *vd =
> (struct acpi_video_device *)bl_get_data(bd);
> - acpi_video_device_lcd_set_level(vd, request_level);
> + acpi_video_device_lcd_set_level(vd,
> + vd->brightness->levels[request_level]);
> return 0;
> }
>
> @@ -656,7 +664,6 @@ static void acpi_video_device_find_cap(struct acpi_video_device *device)
> kfree(obj);
>
> if (device->cap._BCL && device->cap._BCM && device->cap._BQC && max_level > 0){
> - unsigned long tmp;
> static int count = 0;
> char *name;
> name = kzalloc(MAX_NAME_LEN, GFP_KERNEL);
> @@ -664,11 +671,10 @@ static void acpi_video_device_find_cap(struct acpi_video_device *device)
> return;
>
> sprintf(name, "acpi_video%d", count++);
> - acpi_video_device_lcd_get_level_current(device, &tmp);
> device->backlight = backlight_device_register(name,
> NULL, device, &acpi_backlight_ops);
> - device->backlight->props.max_brightness = max_level;
> - device->backlight->props.brightness = (int)tmp;
> + device->backlight->props.max_brightness = device->brightness->count-3;
> + device->backlight->props.brightness = acpi_video_get_brightness(device->backlight);
> backlight_update_status(device->backlight);
>
> kfree(name);
>
next prev parent reply other threads:[~2008-01-24 21:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-26 2:03 [PATCH] Rationalise ACPI backlight implementation Matthew Garrett
2008-01-14 1:51 ` Matthew Garrett
2008-01-22 8:33 ` Zhang Rui
2008-01-22 11:46 ` Matthew Garrett
2008-01-22 12:39 ` Henrique de Moraes Holschuh
2008-01-24 21:44 ` Len Brown [this message]
2008-01-27 2:06 ` Matthew Garrett
2008-01-27 6:00 ` Andrew Morton
2008-01-28 1:25 ` Matthew Garrett
2008-01-28 5:10 ` Andrew Morton
2008-01-28 5:28 ` Matthew Garrett
2008-01-28 15:51 ` Henrique de Moraes Holschuh
2008-02-02 3:46 ` Len Brown
2008-02-02 11:30 ` Henrique de Moraes Holschuh
2008-02-06 10:09 ` Romano Giannetti
2008-02-06 10:09 ` Romano Giannetti
2008-02-02 3:43 ` Len Brown
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=200801241644.49114.lenb@kernel.org \
--to=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.