public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
Cc: "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: Tue, 19 Aug 2014 16:29:32 +0300	[thread overview]
Message-ID: <87iolohakj.fsf@intel.com> (raw)
In-Reply-To: <7955720e6579951f4da64388ab4e1673.squirrel@webmail1.one.com>

On Tue, 19 Aug 2014, Bertrik Sikken <bertrik@sikken.nl> wrote:
>> On Sun, 17 Aug 2014, Bertrik Sikken <bertrik@sikken.nl> wrote:
>>> On 15-8-2014 3:43, Jani Nikula wrote:
>>>> On Thu, 14 Aug 2014, Bertrik Sikken <bertrik@sikken.nl> wrote:
>>>
>>>>> Attached is dmesg output from booting kernel 3.14-2 (debian unstable)
>>>>> with drm.debug=0xe and the samsung_laptop module enabled, from my
>>>>> Samsung N150plus netbook.
>>>>
>>>> Have you tried 3.15?
>>>
>>> I've built the v3.15 kernel (using the .config file from debian
>>> unstable and doing make oldconfig).
>>>
>>> The backlight is at maximum brightness after boot and I can't control
>>> it using the backlight buttons, nor by writing to
>>> /sys/class/backlight/samsung/brightness
>>> (say half the value or 1/10th of max_brightness)
>>>
>>> Backlight does work when writing
>>> /sys/class/backlight/intel_backlight/brightness
>>
>> How about disabling samsung backlight module with 3.15?
>
> I'm not sure what you mean by that.
>
> As I understand it, there are three ways to control the backlight on this
> netbook: using intel_backlight, samsung_laptop (using a "sabi" interface)
> and acpi_video.
> Backlight control using the samsung_laptop driver no longer seems to work
> after the change. If I disable it (e.g. by blacklisting it), I expect it
> to no longer work at all obviously.
>
> What do you want me to test exactly?

If the intel_backlight interface works in 3.15, I presume the problem is
that you have a non-functional samsung backlight interface that is
preferred over intel_backlight by your userspace.

BR,
Jani.



>
> Kind regards,
> Bertrik
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Jani Nikula, Intel Open Source Technology Center

  reply	other threads:[~2014-08-19 13:29 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
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 [this message]
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=87iolohakj.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=bertrik@sikken.nl \
    --cc=intel-gfx@lists.freedesktop.org \
    /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