From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Zhang Rui <rui.zhang@intel.com>, Len Brown <lenb@kernel.org>,
Vincent Gerris <vgerris@gmail.com>,
linux-acpi@vger.kernel.org
Subject: Re: [RFC PATCH] acpi: mv models with win8 brightness problems from win8 blacklist to use_native_backlight
Date: Thu, 01 May 2014 20:51:58 +0200 [thread overview]
Message-ID: <2095093.jbbehouB3C@vostro.rjw.lan> (raw)
In-Reply-To: <536220E7.7010805@redhat.com>
On Thursday, May 01, 2014 12:24:39 PM Hans de Goede wrote:
> Hi,
>
> On 04/30/2014 09:56 PM, Rafael J. Wysocki wrote:
> > On Wednesday, April 30, 2014 03:48:46 PM Hans de Goede wrote:
> >> When the windows8 related backlight problems became evident, 2 approaches
> >> were follow in paralellel, one was to stop claiming to be windows 8 / 2012,
> >> the other was to tell acpi_video to stop registering a backlight driver.
> >>
> >> I've read all the threads and it seems that which approach ended up being
> >> applied to which model laptop was never really a concious decision (AFAIK).
> >>
> >> So lets move all the models which are only on the win8 blacklist because of
> >> brightness issues to the use_native_backlight list, which is the smaller
> >> hammer to use to solve the backlight issues.
> >>
> >> Note: this is not tested on any of the affected models, this just seems like
> >> the sensible thing to do.
> >>
> >> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
> >
> > Since commit 170269a9d3c0 (ACPI / video: Default to using native backlight
> > control on Windows 8 systems) in linux-next is effectively removing the black
> > list from video.c, I guess what you really would like to do would be to drop
> > the items from blacklist.c. If so, please submit a patch to remove them on
> > top of commit 170269a9d3c0.
>
> Right, the RFC was mostly for discussing what to do in case commit 170269a9d3c0
> does not work out well and ends up being reverted (as this was tried before and
> got reverted pretty quickly).
>
> I'll send a patch just removing all the entries for -next for now, and I'll try
> to remember that we need a patch like this RFC if we end up reverting.
OK, thanks!
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
prev parent reply other threads:[~2014-05-01 18:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-30 13:48 [RFC PATCH] acpi: mv models with win8 brightness problems from win8 blacklist to use_native_backlight Hans de Goede
2014-04-30 19:56 ` Rafael J. Wysocki
2014-05-01 10:24 ` Hans de Goede
2014-05-01 18:51 ` Rafael J. Wysocki [this message]
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=2095093.jbbehouB3C@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=hdegoede@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=vgerris@gmail.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