All of lore.kernel.org
 help / color / mirror / Atom feed
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: Sat, 29 Nov 2014 21:01:47 +0800	[thread overview]
Message-ID: <5479C3BB.5080905@intel.com> (raw)
In-Reply-To: <20141128171812.GA3658@norris-Latitude-E6410>

On 11/29/2014 01:18 AM, Brian Norris wrote:
> On Fri, Nov 28, 2014 at 07:55:00PM +0800, Aaron Lu wrote:
>> On 11/28/2014 05:59 PM, Brian Norris wrote:
>>> 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.
> 
> Appending dmesg and attaching acpidump. Unfortunately, I'm using a few
> binary modules, since Wifi and GPU suspend/resume support are broken
> otherwise, but I did test briefly with Nouveau anyway. Results are
> essentially the same with Nouveau (although Nouveau seems to provide an
> extra backlight device, though it doesn't seem to do anything for me).
> 
> Before reverting:
> 
> $ ls -al /sys/class/backlight
> total 0
> drwxr-xr-x  2 root root 0 Nov 28 09:01 .
> drwxr-xr-x 58 root root 0 Nov 28 09:01 ..
> 
> After reverting:
> 
> $ ls -al /sys/class/backlight
> total 0
> drwxr-xr-x  2 root root 0 Nov 28 09:10 .
> drwxr-xr-x 50 root root 0 Nov 28 09:10 ..
> lrwxrwxrwx  1 root root 0 Nov 28 09:09 acpi_video0 -> ../../devices/pci0000:00/0000:00:01.0/0000:01:00.0/backlight/acpi_video0

The current logic to bind device doesn't work with your system, that
logic is there for a long time so I prefer not to change that, instead,
I can change the newly added function acpi_video_device_in_dod to let it
directly compare the 0-12 bits of the ID to decide if the video output
device is in the _DOD list. Can you please try the following patch?

diff --git a/drivers/acpi/video.c b/drivers/acpi/video.c
index 41e6b977ceb2..185a57d13723 100644
--- a/drivers/acpi/video.c
+++ b/drivers/acpi/video.c
@@ -1164,7 +1164,8 @@ static bool acpi_video_device_in_dod(struct acpi_video_device *device)
 		return true;
 
 	for (i = 0; i < video->attached_count; i++) {
-		if (video->attached_array[i].bind_info == device)
+		if ((video->attached_array[i].value.int_val & 0xfff) ==
+		    (device->device_id & 0xfff))
 			return true;
 	}
 

Thanks,
Aaron

  reply	other threads:[~2014-11-29 13:01 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
2014-11-28 17:18         ` Brian Norris
2014-11-29 13:01           ` Aaron Lu [this message]
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=5479C3BB.5080905@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.