From: "Bjørn Mork" <bjorn@mork.no>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Hans de Goede <hdegoede@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux ACPI <linux-acpi@vger.kernel.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Subject: Re: [BISECTED 3.16-rc REGREGRESSION] backlight control stopped working
Date: Mon, 14 Jul 2014 23:46:22 +0200 [thread overview]
Message-ID: <8761iztxzl.fsf@nemi.mork.no> (raw)
In-Reply-To: <CA+55aFztNg4aFUnmqxoR-Hwva87D1TMOZ2Gyy8CVmEov9ToDQg@mail.gmail.com> (Linus Torvalds's message of "Mon, 14 Jul 2014 13:49:10 -0700")
Linus Torvalds <torvalds@linux-foundation.org> writes:
> On Mon, Jul 14, 2014 at 1:45 PM, Bjørn Mork <bjorn@mork.no> wrote:
>>> brightness change from user mode comes in during that delay, we cancel
>>> the kernel-induced pending change.
>>
>> That sounds like a good solution to me FWIW.
>
> Try the patch. It *might* work. I'm not saying it will, but it seemed
> to at least compile for me.
Yes, the patch works as advertised for me. Thanks.
But this will break existing configs:
> --- a/drivers/acpi/video.c
> +++ b/drivers/acpi/video.c
> @@ -68,8 +68,8 @@ MODULE_AUTHOR("Bruno Ducrot");
> MODULE_DESCRIPTION("ACPI Video Driver");
> MODULE_LICENSE("GPL");
>
> -static bool brightness_switch_enabled;
> -module_param(brightness_switch_enabled, bool, 0644);
> +static int brightness_switch_enabled = -1;
> +module_param(brightness_switch_enabled, int, 0644);
>
> /*
> * By default, we don't allow duplicate ACPI video bus devices
Any setup using e.g "options video brightness_switch_enabled=Y" will
barf on this, won't they?
Bjørn
--
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-14 21:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 12:59 [BISECTED 3.16-rc REGREGRESSION] backlight control stopped working Bjørn Mork
2014-07-14 13:14 ` Hans de Goede
2014-07-14 13:27 ` Bjørn Mork
2014-07-14 16:24 ` Linus Torvalds
2014-07-14 16:59 ` Linus Torvalds
2014-07-14 20:45 ` Bjørn Mork
2014-07-14 20:49 ` Linus Torvalds
2014-07-14 21:46 ` Bjørn Mork [this message]
2014-07-14 22:19 ` Linus Torvalds
2014-07-14 18:01 ` Rafael J. Wysocki
2014-07-15 7:00 ` Hans de Goede
2014-07-15 7:33 ` Bjørn Mork
2014-07-15 10:59 ` Hans de Goede
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=8761iztxzl.fsf@nemi.mork.no \
--to=bjorn@mork.no \
--cc=hdegoede@redhat.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--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