public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Luis Ortega <luiorpe1@upv.es>
Cc: daniel.vetter@ffwll.ch, airlied@linux.ie,
	intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org
Subject: Re: [Regression 3.14-rc2] drm/i915: Brightness adjustment is broken in 945GM
Date: Thu, 13 Feb 2014 17:04:23 +0200	[thread overview]
Message-ID: <87lhxfvytk.fsf@intel.com> (raw)
In-Reply-To: <20140213153458.GA724@Len.lan_dn>

On Thu, 13 Feb 2014, Luis Ortega <luiorpe1@upv.es> wrote:
> Hi, testing 3.14-rc2 I noticed I could not adjust the brightness of the
> screen any longer. This problem is already present in 3.14-rc1. 3.13 works fine.
>
> My hardware is a netbook with intel atom and a 945GM graphics card.
>
> I bisected the problem down to the next commit:

I dare say either your bisect went sour or you don't have 945GM. Please
verify your steps.

Please provide dmesg with drm.debug=0xe with 3.14-rc2.

BR,
Jani.

>
> bc0bb9fd1c7810407ab810d204bbaecb255fddde is the first bad commit
> commit bc0bb9fd1c7810407ab810d204bbaecb255fddde
> Author: Jani Nikula <jani.nikula@intel.com>
> Date:   Thu Nov 14 12:14:29 2013 +0200
>
>     drm/i915: remove QUIRK_NO_PCH_PWM_ENABLE
>     
>     The quirk was added as what I'd say was a stopgap measure in
>     
>     commit e85843bec6c2ea7c10ec61238396891cc2b753a9
>     Author: Kamal Mostafa <kamal@canonical.com>
>     Date:   Fri Jul 19 15:02:01 2013 -0700
>     
>         drm/i915: quirk no PCH_PWM_ENABLE for Dell XPS13 backlight
>     
>     without really digging into what was going on.
>     
>     Also, as mentioned in the related bug [1], having the quirk regressed
>     some of the machines it was supposed to fix to begin with, and there
>     were patches posted to disable the quirk on such machines [2]!
>     
>     The fact is, we do need the BLM_PCH_PWM_ENABLE bit set to have
>     backlight. With the quirk, we've relied on BIOS to have set it, and our
>     save/restore code to retain it. With the full backlight setup at enable,
>     we have no place for things that rely on previous state.
>     
>     With the per platform hooks, we've also made a change in the PCH
>     platform enable order: setting the backlight duty cycle between CPU and
>     PCH PWM enable. Some experimenting and
>     
>     commit 770c12312ad617172b1a65b911d3e6564fc5aca8
>     Author: Takashi Iwai <tiwai@suse.de>
>     Date:   Sat Aug 11 08:56:42 2012 +0200
>     
>         drm/i915: Fix blank panel at reopening lid
>     
>     indicate that we can't set the backlight before enabling CPU PWM; the
>     value just won't stick. But AFAICT we should do it before enabling the
>     PCH PWM.
>     
>     Finally, any fallout we should fix properly, preferrably without quirks,
>     and absolutely without quirks that rely on existing state. With the per
>     platform hooks have much more flexibility to adjust the sequence as
>     required by platforms.
>     
>     [1] https://bugzilla.kernel.org/show_bug.cgi?id=47941
>     [2] http://lkml.kernel.org/r/1378229848-29113-1-git-send-email-kamal@canonical.com
>     
>     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>
>
>
> Additionally, when I had narrowed the problem to around 11 commits all the
> resulting kernel I compiled made the screen blink and shake from left to right
> non-stop. In the -rc kernels this doesn't happen. Thought it was worth
> mentioning.


-- 
Jani Nikula, Intel Open Source Technology Center

  reply	other threads:[~2014-02-13 15:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-13 15:34 [Regression 3.14-rc2] drm/i915: Brightness adjustment is broken in 945GM Luis Ortega
2014-02-13 15:04 ` Jani Nikula [this message]
2014-02-13 16:24   ` Luis Ortega
2014-02-13 20:58     ` Luis Ortega
2014-02-14  7:09       ` Jani Nikula
2014-02-14 20:46         ` Luis Ortega

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=87lhxfvytk.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=airlied@linux.ie \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiorpe1@upv.es \
    /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