From: Thomas Richter <richter@rus.uni-stuttgart.de>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Intel Graphics Development" <intel-gfx@lists.freedesktop.org>
Subject: Re: S6010 - brightness adjustment not available
Date: Sat, 16 Aug 2014 20:25:42 +0200 [thread overview]
Message-ID: <53EFA226.3090102@rus.uni-stuttgart.de> (raw)
In-Reply-To: <20140816181342.GU4193@intel.com>
Hi Ville
>> just testing your alm_fixes11 branch. So far, everything works fine,
>> including suspend2ram, for the first time! Yippiee!
>>
>> However, there is one thing that bothers me, namely that the brightness
>> adjustment is no longer working. Specifically, fujitsu_laptop fails with:
>>
>> Fujitsu laptop FUJ02B1 ACPI brightness driver: probe of FUJ02B1:00
>> failed with error -22
>
> My impression was that those were happening since forever. But I can't
> be sure.
Actually, it did work with the alm-fixes5 patch, based on 3.15.0 rc7+ IIRC.
>> The source of fujitsu_laptop does not seem to have changed, thus I
>> believe it must be somehow related to the modifications you made. Any
>> idea where to look?
>
> Hmm. My impression was that the backlight control is handled by some
> hardware/firmware magic and OS can't touch it. IIRC that's how it seemed
> to work on my 855 machine which is a slighly newer Fujitsu-Siemens
> Lifebook model. At least on that machine backlight buttons worked
> a while ago.
Oh, sorry, I should have clarified. Yes, the *buttons* work, those are
handled by the firmware (via the Bios service management interrupt, I
suppose), but usually the fujitsu-laptop module *also* creates a device
which provides access to the brightness control such that tools like the
Gnome brightness applet can pick the information up and allows
user-control of the brightness. The corresponding device does no longer
exist on 3.16.0. Not yet fully clear whether that's due to the patches
you made or something else, but I was running out of time yesterday to
start a bisection, and I'm currently on the road and cannot test
(greetings from Newark airport, BTW.)
> I can re-test the s6010 backlight next week and see if it works for me.
>
> I guess one idea might be the "init important ns2501 registers" patch.
No, I don't think so. You had that in in alm_fixes5 already, and there
it worked. So the DVO is innocent, at least this time. As said, I
haven't had the chance to have a more detailed look, but it seems that
the fujitsu laptop extras go through some scary ACPI access path to
control the backlight, and somehow this seems to be broken now, for a
reason I haven't tried to understand.
> Maybe the values I used weren't entirely correct for this machine and
> we need to use the exact same values as the BIOS. All the other register
> values I used were definitely the same that hte BIOS set up, but I have
> nagging feeling there was some slight difference with these few
> registers.
Probably try something else first if you get the chance. My next
possibility to work on this is next Saturday when I'm back from San
Diego (this is where I'm going right now) and then take out your patches
one by one.
Greetings,
Thomas
next prev parent reply other threads:[~2014-08-16 18:25 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-14 22:21 [PATCH 00/16] drm/i915: 830M/ns201 fixes again ville.syrjala
2014-08-14 22:21 ` [PATCH 01/16] drm/i915: Fix gen2 planes B and C max watermark value ville.syrjala
2014-08-15 13:25 ` Thomas Richter
2014-08-14 22:21 ` [PATCH 02/16] drm/i915: Disable trickle feed for gen2/3 ville.syrjala
2014-08-14 22:21 ` [PATCH 03/16] drm/i915: Idle unused rings on gen2/3 during init/resume ville.syrjala
2014-08-14 22:21 ` [PATCH 04/16] drm/i915: Pass intel_crtc to intel_disable_pipe() and intel_wait_for_pipe_off() ville.syrjala
2014-08-15 13:27 ` Thomas Richter
2014-08-14 22:21 ` [PATCH v3 05/16] drm/i915: Disable double wide even when leaving the pipe on ville.syrjala
2014-08-15 13:28 ` Thomas Richter
2014-08-14 22:21 ` [PATCH 06/16] drm/i915: ns2501 is on DVOB ville.syrjala
2014-08-15 13:29 ` Thomas Richter
2014-08-14 22:21 ` [PATCH 07/16] drm/i915: Enable DVO between mode_set and dpms hooks ville.syrjala
2014-08-15 13:29 ` Thomas Richter
2014-08-14 22:22 ` [PATCH 08/16] drm/i915: Don't call DVO mode_set hook on DPMS changes ville.syrjala
2014-08-15 13:30 ` Thomas Richter
2014-08-14 22:22 ` [PATCH 09/16] drm/i915: Kill useless ns2501_dump_regs ville.syrjala
2014-08-15 13:08 ` Thomas Richter
2014-08-15 13:31 ` Thomas Richter
2014-08-14 22:22 ` [PATCH 10/16] drm/i915: Rewrite ns2501 driver a bit ville.syrjala
2014-08-15 13:13 ` Thomas Richter
2014-08-15 13:32 ` Thomas Richter
2014-08-14 22:22 ` [PATCH 11/16] drm/i915: Init important ns2501 registers ville.syrjala
2014-08-15 13:18 ` Thomas Richter
2014-08-15 13:33 ` Thomas Richter
2014-09-01 8:42 ` Daniel Vetter
2014-08-14 22:22 ` [PATCH 12/16] drm/i915: Check pixel clock in ns2501 mode_valid hook ville.syrjala
2014-08-15 13:19 ` Thomas Richter
2014-08-15 13:33 ` Thomas Richter
2014-08-14 22:22 ` [PATCH 13/16] drm/i915: Fix DVO 2x clock enable on 830M ville.syrjala
2014-08-15 13:34 ` Thomas Richter
2014-09-01 8:46 ` Daniel Vetter
2014-09-05 18:52 ` [PATCH v2 " ville.syrjala
2014-09-08 7:33 ` Daniel Vetter
2014-08-14 22:22 ` [PATCH 14/16] Revert "drm/i915: Nuke pipe A quirk on i830M" ville.syrjala
2014-08-15 13:36 ` Thomas Richter
2014-08-14 22:22 ` [PATCH v2 15/16] drm/i915: Add pipe B force quirk for 830M ville.syrjala
2014-08-15 13:37 ` Thomas Richter
2014-08-14 22:22 ` [PATCH 16/16] drm/i915: Preserve VGACNTR bits from the BIOS ville.syrjala
2014-08-15 13:39 ` Thomas Richter
2014-08-15 7:57 ` [PATCH 00/16] drm/i915: 830M/ns201 fixes again Ville Syrjälä
[not found] ` <53EE59E8.7030101@rus.uni-stuttgart.de>
[not found] ` <20140816181342.GU4193@intel.com>
2014-08-16 18:25 ` Thomas Richter [this message]
2014-08-16 20:34 ` S6010 - brightness adjustment not available Ville Syrjälä
2014-09-01 8:53 ` [PATCH 00/16] drm/i915: 830M/ns201 fixes again Daniel Vetter
2014-09-05 18:54 ` [PATCH] drm/i915: Limit the watermark to at least 8 entries on gen2/3 ville.syrjala
2014-09-05 19:03 ` Thomas Richter
2014-09-06 17:33 ` Ville Syrjälä
2014-09-06 17:50 ` Thomas Richter
2014-09-08 7:39 ` Daniel Vetter
2014-09-08 7:41 ` Thomas Richter
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=53EFA226.3090102@rus.uni-stuttgart.de \
--to=richter@rus.uni-stuttgart.de \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox