From: Aaron Lu <aaron.lu@intel.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
ntrrgc@gmail.com,
ACPI Devel Mailing List <linux-acpi@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ACPI / video: check _DOD list when creating backlight device
Date: Fri, 28 Nov 2014 19:55:00 +0800 [thread overview]
Message-ID: <54786294.5030105@intel.com> (raw)
In-Reply-To: <20141128095928.GA5106@norris-Latitude-E6410>
On 11/28/2014 05:59 PM, Brian Norris wrote:
> On Thu, Oct 09, 2014 at 04:27:55PM +0800, Aaron Lu wrote:
>> On 10/01/2014 04:18 AM, Rafael J. Wysocki wrote:
>>> On Tuesday, September 30, 2014 02:10:17 PM Aaron Lu wrote:
>>>> The _DOD method lists which video output device is currently attached so
>>>> we should only care about them and ignore others. An user recently
>>>> reported that there are two acpi_video interfaces appeared on his system
>>>> and one of them doesn't work. From the acpidump, it is found that there
>>>> are more than one video output devices that have _BCM control method but
>>>> the _DOD lists only one of them. So this patch checks if the video output
>>>> device is in the _DOD list and will not create backlight device if it is
>>>> not in the list. Also, we consider the broken _DOD case(reflected by the
>>>> video->attached_count is 0) and do not change behaviour for those broken
>>>> _DOD systems.
>>>>
>>>> Buglink: https://bugzilla.kernel.org/show_bug.cgi?id=84111
>>>> Reported-and-tested-by: ntrrgc@gmail.com
>>>> Signed-off-by: Aaron Lu <aaron.lu@intel.com>
>>>
>>> This looks reasonable to me, but I'm a little afraid that it may break
>>> systems which forget to list valid interfaces in the _DOD.
>>
>> Indeed, this is possible.
>
> And indeed, there is a regression! My Dell Latituded E6410's backlight
> control no longer works after this commit, and I get messages like this
> instead:
>
> [ 57.214610] ACPI: Failed to switch the brightness
>
> If I revert this commit, my backlight controls work again. Also, I
> regain a cooling device (?) that was being ignored:
>
> [ 1.332682] acpi device:02: registered as cooling_device0
>
> Do you need any additional info to handle the regression, or should we
> just revert the patch?
Please attach acpidump, dmesg with video.dyndbg="module video +pft" in
kernel cmdline, list the /sys/class/backlight with and without this
commit, thanks.
-Aaron
>
> Brian
>
next prev parent reply other threads:[~2014-11-28 11:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 6:10 [PATCH] ACPI / video: check _DOD list when creating backlight device Aaron Lu
2014-09-30 20:18 ` Rafael J. Wysocki
2014-10-09 8:27 ` Aaron Lu
2014-11-28 9:59 ` Brian Norris
2014-11-28 11:55 ` Aaron Lu [this message]
2014-11-28 17:18 ` Brian Norris
2014-11-29 13:01 ` Aaron Lu
2014-11-29 17:34 ` Brian Norris
2014-11-30 1:14 ` [PATCH] ACPI / video: update the condition to check if a device is in _DOD list Aaron Lu
2014-12-03 2:25 ` 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=54786294.5030105@intel.com \
--to=aaron.lu@intel.com \
--cc=computersforpeace@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ntrrgc@gmail.com \
--cc=rjw@rjwysocki.net \
/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).