linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Aaron Lu <aaron.lwe@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Felipe Contreras <felipe.contreras@gmail.com>,
	linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
	Len Brown <lenb@kernel.org>, Zhang Rui <rui.zhang@intel.com>
Subject: Re: [PATCH] acpi: video: improve quirk check
Date: Sat, 03 Aug 2013 16:14:04 +0800	[thread overview]
Message-ID: <51FCBBCC.6060307@gmail.com> (raw)
In-Reply-To: <3682340.ddGL4l7l22@vostro.rjw.lan>

On 08/03/2013 07:47 AM, Rafael J. Wysocki wrote:
> On Friday, August 02, 2013 02:37:09 PM Felipe Contreras wrote:
>> If the _BCL package is descending, the first level (br->levels[2]) will
>> be 0, and if the number of levels matches the number of steps, we might
>> confuse a returned level to mean the index.
>>
>> For example:
>>
>>   current_level = max_level = 100
>>   test_level = 0
>>   returned level = 100
>>
>> In this case 100 means the level, not the index, and _BCM failed. But if
>> the _BCL package is descending, the index of level 0 is also 100, so we
>> assume _BQC is indexed, when it's not.
>>
>> This causes all _BQC calls to return bogus values causing weird behavior
>> from the user's perspective. For example: xbacklight -set 10; xbacklight
>> -set 20; would flash to 90% and then slowly down to the desired level
>> (20).
>>
>> The solution is simple; test anything other than the first level (e.g.
>> 1).
>>
>> Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
> 
> Looks reasonable.
> 
> Aaron, what do you think?

Yes, the patch is correct, but I still prefer my own version :-)
https://github.com/aaronlu/linux/commit/0a3d2c5b59caf80ae5bb1ca1fda0f7bf448b38c9

In case you want to take mine and mine needs refresh, please let me know
and I can do the re-base, thanks.

-Aaron

> 
> Rafael
> 
> 
>> ---
>>
>> On top of this we might want to test yet another value, because br->levels[3]
>> might be the current value (although very unlikely).
>>
>>  drivers/acpi/video.c | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/acpi/video.c b/drivers/acpi/video.c
>> index 0ec434d..e1284b8 100644
>> --- a/drivers/acpi/video.c
>> +++ b/drivers/acpi/video.c
>> @@ -689,7 +689,7 @@ static int acpi_video_bqc_quirk(struct acpi_video_device *device,
>>  	 * Some systems always report current brightness level as maximum
>>  	 * through _BQC, we need to test another value for them.
>>  	 */
>> -	test_level = current_level == max_level ? br->levels[2] : max_level;
>> +	test_level = current_level == max_level ? br->levels[3] : max_level;
>>  
>>  	result = acpi_video_device_lcd_set_level(device, test_level);
>>  	if (result)
>>


  parent reply	other threads:[~2013-08-03  8:13 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-02 19:37 [PATCH] acpi: video: improve quirk check Felipe Contreras
2013-08-02 23:47 ` Rafael J. Wysocki
2013-08-03  1:04   ` Felipe Contreras
2013-08-03  1:16     ` Rafael J. Wysocki
2013-08-03  1:07       ` Felipe Contreras
2013-08-03  1:19         ` Rafael J. Wysocki
2013-08-03  1:30           ` Felipe Contreras
2013-08-03  8:14   ` Aaron Lu [this message]
2013-08-03 11:34     ` Rafael J. Wysocki
2013-08-03 20:24       ` Felipe Contreras
2013-08-03 21:40         ` Rafael J. Wysocki
2013-08-03 22:20           ` Felipe Contreras
2013-08-03 22:38             ` Rafael J. Wysocki
2013-08-03 22:37               ` Felipe Contreras
2013-08-04  1:47             ` Aaron Lu
2013-08-04  6:54               ` Felipe Contreras
2013-08-04 14:14                 ` Rafael J. Wysocki
2013-08-04 14:08                   ` Felipe Contreras
2013-08-04  1:18       ` Aaron Lu
2013-08-04  6:42         ` Felipe Contreras
2013-08-04 14:19           ` Rafael J. Wysocki
2013-08-04 14:19             ` Felipe Contreras
2013-08-05 14:04               ` Rafael J. Wysocki
2013-08-05 14:41                 ` Felipe Contreras
2013-08-07  4:35               ` Aaron Lu

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=51FCBBCC.6060307@gmail.com \
    --to=aaron.lwe@gmail.com \
    --cc=felipe.contreras@gmail.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=rui.zhang@intel.com \
    /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;
as well as URLs for NNTP newsgroup(s).