linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>, linux-acpi@vger.kernel.org
Subject: Re: [PATCH] acpi-video: Add disable_native_backlight quirk for Dell XPS15 L521X
Date: Mon, 12 Jan 2015 10:12:57 +0100	[thread overview]
Message-ID: <54B39019.2070501@redhat.com> (raw)
In-Reply-To: <20150112024411.GA6831@srcf.ucam.org>

Hi,

On 12-01-15 03:44, Matthew Garrett wrote:
> On Sun, Jan 11, 2015 at 11:37:52AM +0100, Hans de Goede wrote:
>
>> Userspace is writing to the intel_backlight device because it is the
>> only one present under /sys/class/backlight, as we disable acpi-video
>> on win8 ready laptops by default now.
>
> Why is nouveau not providing a backlight device?

I do not know.

>> The commit message may not be 100% accurate, although I believe this is
>> related to the laptop having nvidia graphics, but the code / fix is correct
>> regardless.
>
> I don't think we have enough evidence to know whether this fix is
> correct.

This fix fixes a regression introduced from kernel 3.15 to 3.16, when we
switched video.use_native_brightness's default from 0 to 1, all this patch
does is restore the previous behaviour on this specific model as the new
behaviour is broken.

So this is in essence a model targeted "revert" fixing a regression and as
such most certainly is correct, given the clear no regressions policy the
kernel has.

Might it be good to dive deeper as to why the intel_backlight interface
does not work, yes certainly.

Regards,

Hans

  reply	other threads:[~2015-01-12  9:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-05  7:57 [PATCH] acpi-video: Add disable_native_backlight quirk for Dell XPS15 L521X Hans de Goede
2015-01-05 23:35 ` Rafael J. Wysocki
2015-01-11  6:16 ` Matthew Garrett
2015-01-11 10:37   ` Hans de Goede
2015-01-12  2:44     ` Matthew Garrett
2015-01-12  9:12       ` Hans de Goede [this message]
2015-01-12 10:21         ` Matthew Garrett

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=54B39019.2070501@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --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).