public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Aaron Lu <aaron.lu@intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>,
	ACPI Devel Mailing List <linux-acpi@vger.kernel.org>
Cc: Dmitry Tunin <hanipouspilot@gmail.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>, Jimbo <jaime.91@hotmail.es>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Oleksij Rempel <linux@rempel-privat.de>
Subject: Re: [PATCH] ACPI / video: update the skip case for acpi_video_device_in_dod
Date: Tue, 16 Dec 2014 11:21:15 +0800	[thread overview]
Message-ID: <548FA52B.6060602@intel.com> (raw)
In-Reply-To: <87r3w1jnf6.fsf@intel.com>

On 12/15/2014 05:02 PM, Jani Nikula wrote:
> On Mon, 15 Dec 2014, Aaron Lu <aaron.lu@intel.com> wrote:
>> If the firmware has declared more than 8 video output devices, and the
>> one that control the internal panel's backlight is listed after the
>> first 8 output devices, the _DOD will not include it due to the current
>> i915 operation region implementation. As a result, we will not create a
>> backlight device for it while we should. Solve this problem by special
>> case the firmware that has 8+ output devices in that if we see such a
>> firmware, we do not test if the device is in _DOD list. The creation of
>> the backlight device will also enable the firmware to emit events on
>> backlight hotkey press when the acpi_osi= cmdline option is specified on
>> those affected ASUS laptops.
>>
>> Buglink: https://bugzilla.kernel.org/show_bug.cgi?id=70241
>> Reported-and-tested-by: Oleksij Rempel <linux@rempel-privat.de>
>> Reported-and-tested-by: Dmitry Tunin <hanipouspilot@gmail.com>
>> Reported-and-tested-by: Jimbo <jaime.91@hotmail.es>
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Aaron Lu <aaron.lu@intel.com>
> 
> Obviously I'd like to have the proper information in the opregion
> DIDL/CADL fields, but it's not going to happen soon, nor is it going to
> fit under stable size limits.
> 
> I like the simplicity here. FWIW,
> 
> Acked-by: Jani Nikula <jani.nikula@intel.com>

Thanks :-)

BTW, this patch is more of a fix for my previous commit 0b8db271f159
("ACPI / video: check _DOD list when creating backlight devices") that
made the acpi_video interface disappear on these affected laptops so I
would like to fix it quickly. And I agree that a proper implementation
of the DIDL/CADL list is needed so that people can get rid of the
acpi_osi= cmdline option they currently need to get hotkey events.

Regards,
Aaron

> 
>> ---
>>  drivers/acpi/video.c | 10 ++++++++--
>>  1 file changed, 8 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/acpi/video.c b/drivers/acpi/video.c
>> index 8b844931b936..c72e79d2c5ad 100644
>> --- a/drivers/acpi/video.c
>> +++ b/drivers/acpi/video.c
>> @@ -155,6 +155,7 @@ struct acpi_video_bus {
>>  	u8 dos_setting;
>>  	struct acpi_video_enumerated_device *attached_array;
>>  	u8 attached_count;
>> +	u8 child_count;
>>  	struct acpi_video_bus_cap cap;
>>  	struct acpi_video_bus_flags flags;
>>  	struct list_head video_device_list;
>> @@ -1176,8 +1177,12 @@ static bool acpi_video_device_in_dod(struct acpi_video_device *device)
>>  	struct acpi_video_bus *video = device->video;
>>  	int i;
>>  
>> -	/* If we have a broken _DOD, no need to test */
>> -	if (!video->attached_count)
>> +	/*
>> +	 * If we have a broken _DOD or we have more than 8 output devices
>> +	 * under the graphics controller node that we can't proper deal with
>> +	 * in the operation region code currently, no need to test.
>> +	 */
>> +	if (!video->attached_count || video->child_count > 8)
>>  		return true;
>>  
>>  	for (i = 0; i < video->attached_count; i++) {
>> @@ -1430,6 +1435,7 @@ acpi_video_bus_get_devices(struct acpi_video_bus *video,
>>  			dev_err(&dev->dev, "Can't attach device\n");
>>  			break;
>>  		}
>> +		video->child_count++;
>>  	}
>>  	return status;
>>  }
>> -- 
>> 2.1.0
>>
> 

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2014-12-16  3:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-15  8:01 [PATCH] ACPI / video: update the skip case for acpi_video_device_in_dod Aaron Lu
2014-12-15  9:02 ` Jani Nikula
2014-12-16  3:21   ` Aaron Lu [this message]
2014-12-17  0:28     ` 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=548FA52B.6060602@intel.com \
    --to=aaron.lu@intel.com \
    --cc=hanipouspilot@gmail.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jaime.91@hotmail.es \
    --cc=jani.nikula@linux.intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux@rempel-privat.de \
    --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