From: Hans de Goede <hdegoede@redhat.com>
To: "Bjørn Mork" <bjorn@mork.no>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH] acpi-video: Fix backlight taking 2 steps on a brightness key press
Date: Wed, 16 Jul 2014 16:32:36 +0200 [thread overview]
Message-ID: <53C68D04.2030307@redhat.com> (raw)
In-Reply-To: <87wqbdecid.fsf@nemi.mork.no>
Hi,
On 07/16/2014 02:03 PM, Bjørn Mork wrote:
> Hans de Goede <hdegoede@redhat.com> writes:
>
>> Hi All,
>>
>> Here is my cleaned-up version of Linus' patch to fix the 2 steps on a
>> brightness key press problem.
>>
>> Changes compared to Linus' version:
>> -Move the global variables to inside struct acpi_video_device
>> -Rebase on top of Rafael's linux-pm linux-next branch (so on top of the
>> revert of changing the brightness_switch_enabled default)
>>
>> I've tested this on a laptop affected by the 2 steps problem and I can confirm
>> that it fixes the 2 steps issue under normal usage. I managed to trigger the
>> race by generating a heavy io-load, as exptected hitting the race has no
>> unwanted side-effects other then taking 2 steps instead of one.
>>
>> Bjørn can you test this patch on your system and confirm that it does not
>> break things for you please ? Note that in order to apply it you first need
>> to do: "git revert 886129a8eebebec", as the revert has not yet reached
>> Linus' tree AFAIK.
>
> Tested and verified that it still works fine for me, so feel free to add
>
> Tested-by: Bjørn Mork <bjorn@mork.no>
> if you like.
>
Thanks, if there is a need for a v2 I'll add your tested-by.
Rafael, if there is not going to be a v2, could you pick up this tested-by
then?
> But as noted earlier, I believe this poses another risk if anyone has a
> config using bool input values:
>
> -static bool brightness_switch_enabled = 1;
> -module_param(brightness_switch_enabled, bool, 0644);
> +static int brightness_switch_enabled = -1;
> +module_param(brightness_switch_enabled, int, 0644);
>
The only way I can see that being a problem is if someone is using
video.brightness_switch_enabled=N for reasons other then the 2 step
problem this patch fixes. That is not unthinkable though.
> I wonder if it wouldn't be better to just redefine the behaviour of
> "brightness_switch_enabled = 1" to the new delayed response scheme and
> avoid changing the type of this parameter?
I think that is a good idea, that would also allow to simplify the patch
somewhat more. Rafael, what is your take on this ?
Regards,
Hans
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-07-16 14:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 11:25 [PATCH] acpi-video: Fix backlight taking 2 steps on a brightness key press Hans de Goede
2014-07-16 11:25 ` [PATCH] acpi-video: Fix backlight taking 2 steps on a brightness up/down keypress Hans de Goede
2014-07-16 12:03 ` [PATCH] acpi-video: Fix backlight taking 2 steps on a brightness key press Bjørn Mork
2014-07-16 14:32 ` Hans de Goede [this message]
2014-07-16 21:26 ` Rafael J. Wysocki
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=53C68D04.2030307@redhat.com \
--to=hdegoede@redhat.com \
--cc=bjorn@mork.no \
--cc=linux-acpi@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=torvalds@linux-foundation.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