From: Aaron Lu <aaron.lu@intel.com>
To: Danny Baumann <dannybaumann@web.de>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
Zhang Rui <rui.zhang@intel.com>, Len Brown <lenb@kernel.org>
Subject: Re: [PATCH v2 3/3] ACPI video: Fix applying indexed initial brightness value.
Date: Mon, 18 Mar 2013 16:34:27 +0800 [thread overview]
Message-ID: <5146D193.1030104@intel.com> (raw)
In-Reply-To: <5146CFC0.7090907@web.de>
On 03/18/2013 04:26 PM, Danny Baumann wrote:
> Hi,
>
> >> +static unsigned long long
>>> +acpi_video_bqc_value_to_level(struct acpi_video_device *device,
>>> + unsigned long long bqc_value)
>>> +{
>>> + unsigned long long level;
>>> +
>>> + if (device->brightness->flags._BQC_use_index) {
>>> + if (device->brightness->flags._BCL_reversed)
>>> + bqc_value = device->brightness->count - 3 - bqc_value;
>>> +
>>> + level = device->brightness->levels[bqc_value + 2];
>>
>> I don't understand this, what does the +2 have to do here?
>> _BQC returned us an index, and then we should just convert it to level,
>> why +2?
>>
>> The only explanation would be, for BIOS tables that return _BQC as
>> index, they are indexing from the 3rd entry. Is it the case? If so, I
>> think we need to put a comment here.
>
> Yes, that's the case. The old code did the same thing:
Yes, I see that, but I didn't really think about it until reviewing your
patch :-)
>
>>> - if (device->brightness->flags._BQC_use_index) {
>>> - if (device->brightness->flags._BCL_reversed)
>>> - *level = device->brightness->count
>>> - - 3 - (*level);
>>> - *level = device->brightness->levels[*level + 2];
>>> + *level = acpi_video_bqc_value_to_level(device, *level);
>
> That's also the reason for the -3 instead of -1 in the BCL_reversed
> case. I can add a comment, though.
OK, thanks.
That would make people reading the code feel less confused, hopefully.
-Aaron
>
>>> + if (use_bios_initial_backlight) {
>>> + if (!br->flags._BQC_use_index) {
>>> + /*
>>> + * Set the backlight to the initial state.
>>> + * On some buggy laptops, _BQC returns an uninitialized
>>> + * value when invoked for the first time, i.e.
>>> + * level_old is invalid. Set the backlight to max_level
>>> + * in this case.
>>> + */
>>> for (i = 2; i < br->count; i++)
>>> if (level_old == br->levels[i]) {
>>> level = level_old;
>>> break;
>>> }
>>> + } else {
>>> + level = acpi_video_bqc_value_to_level(device,
>>> + level_old);
>>
>> What about we convert the value to level first?
>>
>> if (use_bios_initial_backlight) {
>> level = acpi_video_bqc_value_to_level(device, level_old);
>> /*
>> * Set the backlight to the initial state.
>> * On some buggy laptops, _BQC returns an uninitialized
>> * value when invoked for the first time, i.e.
>> * level_old is invalid(no matter it is a level, or an
>> * index.) Set the backlight to max_level in this case.
>> */
>> for (i = 2; i < br->count; i++)
>> if (level == br->levels[i])
>> break;
>> if (i == br->count)
>> level = max_level;
>> }
>
> That works as well, and looks cleaner to me as well. I'll change that.
>
> Regards,
>
> Danny
>
next prev parent reply other threads:[~2013-03-18 8:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 10:10 [PATCH v2 1/3] ACPI video: Fix brightness control initialization for some laptops Danny Baumann
2013-03-15 10:10 ` [PATCH v2 2/3] ACPI video: Make logic a little easier to understand Danny Baumann
2013-03-15 10:10 ` [PATCH v2 3/3] ACPI video: Fix applying indexed initial brightness value Danny Baumann
2013-03-18 8:16 ` Aaron Lu
2013-03-18 8:26 ` Danny Baumann
2013-03-18 8:34 ` Aaron Lu [this message]
2013-03-18 7:26 ` [PATCH v2 1/3] ACPI video: Fix brightness control initialization for some laptops Aaron Lu
2013-03-18 8:22 ` Danny Baumann
2013-03-18 8:31 ` 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=5146D193.1030104@intel.com \
--to=aaron.lu@intel.com \
--cc=dannybaumann@web.de \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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