All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: "Nikula, Jani" <jani.nikula@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	Bertrik Sikken <bertrik@sikken.nl>
Subject: Re: [REGRESSION BISECTED] backlight control stops workin with 3.14 and later
Date: Wed, 23 Jul 2014 10:46:09 +0200	[thread overview]
Message-ID: <53CF7651.4080305@redhat.com> (raw)
In-Reply-To: <CAKMK7uHzo2R2S6KVT0NJM=vPKBOqM74CGSK-50w4Grpc0qKRkQ@mail.gmail.com>

Hi,

On 07/22/2014 08:52 AM, Daniel Vetter wrote:
> On Tue, Jul 22, 2014 at 8:42 AM, Hans de Goede <hdegoede@redhat.com> wrote:
>> Hi Jani et al,
>>
>> A friend of mine Bertrik Sikken (in the Cc) his backlight control
>> stopped working for him on his Samsung N150Plus netbook.
>>
>> I took a quick look, and the raw intel_backlight backlight interface
>> works under 3.14, but the firmware samsung_laptop backlight interface,
>> which is what most userspace apps will use by default, stops working
>> in 3.14 .
>>
>> I've asked him to bisect this and the bisect points out this
>> commit as the culprit:
>>
>> b35684b8fa94e04f55fd38bf672b737741d2f9e2 is the first bad commit
>> commit b35684b8fa94e04f55fd38bf672b737741d2f9e2
>> Author: Jani Nikula <jani.nikula@intel.com>
>> Date:   Thu Nov 14 12:13:41 2013 +0200
>>
>>     drm/i915: do full backlight setup at enable time
>>
>>     We should now have all the information we need to do a full
>>     initialization of the backlight registers.
>>
>>     v2: Keep QUIRK_NO_PCH_PWM_ENABLE for now (Imre).
>>
>>     Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>>     Reviewed-by: Imre Deak <imre.deak@intel.com>
>>     Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
>>
>> Note that this laptop has an acpi_video backlight interface too,
>> but that has been broken from the start and gets disabled by
>> samsung-laptop based on dmi matching.
> 
> How does the intel backlight fare?

That works fine with 3.14 .

> Please test both 3.14 and 3.15 and

We've tested with 3.14, please let us know if you also want
Bertrik to test with 3.15.

> also test what happens when you blacklist the samsung-laptop driver
> (if that's possible without wreaking the machine).

Then the vendor interface won't get promoted, acpi-video will load,
and things likely will not work.

Bertrik, can you try blacklisting the samsung-laptop module, then
check /sys/class/backlight, the samsung_laptop dir should be gone
replaced by an acpi_video0 (or some such) dir. Please try if that
works. If that does not work, try booting with both the module
blacklisted and "acpi_backlight=vendor" on the kernel commandline,
then you should see only the intel-backlight under /sys/class/backlight
and things should work.

> Also please grab latest intel-gpu-tools and record a register dump
> with intel_reg_dump, again for both broken and working kernels.

Bertrik, can you do this please (without the blacklisting or special
kernel commandline options).

Regards,

Hans

  parent reply	other threads:[~2014-07-23  8:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-22  6:42 [REGRESSION BISECTED] backlight control stops workin with 3.14 and later Hans de Goede
2014-07-22  6:52 ` Daniel Vetter
2014-07-22  6:59   ` Chris Wilson
2014-07-23  8:46   ` Hans de Goede [this message]
2014-07-23 13:15     ` Bertrik Sikken
2014-08-13 13:43     ` Jani Nikula
2014-08-14 19:45       ` Bertrik Sikken
2014-08-15 13:43         ` Jani Nikula
2014-08-17  8:44           ` Bertrik Sikken
2014-08-18  7:37             ` Jani Nikula
2014-08-19  9:52               ` Bertrik Sikken
2014-08-19 13:29                 ` Jani Nikula
2014-08-21 21:44                   ` Bertrik Sikken
2014-08-22  6:48                     ` Jani Nikula
2014-08-22 10:52                       ` Bertrik Sikken
2014-08-23 13:11                       ` Hans de Goede
2014-08-25  7:29                         ` Jani Nikula

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=53CF7651.4080305@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=bertrik@sikken.nl \
    --cc=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.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 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.