Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Jani Nikula <jani.nikula@intel.com>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 3/3] drm/i915: Revert backlight cargo-culting
Date: Fri, 22 Mar 2013 11:00:08 +0100	[thread overview]
Message-ID: <s5h38vnbvpz.wl%tiwai@suse.de> (raw)
In-Reply-To: <1363946021-26651-3-git-send-email-daniel.vetter@ffwll.ch>

At Fri, 22 Mar 2013 10:53:41 +0100,
Daniel Vetter wrote:
> 
> This reverts the following commits:
> 
> cf0a6584aa6d382f802 drm/i915: write backlight harder
> 770c12312ad617172b1 drm/i915: Fix blank panel at reopening lid
> 
> We've come full-circle in this mess and now broke the originally fixed
> machines again with the new trick. So remove it all and start over.
> 
> References: http://www.mail-archive.com/intel-gfx@lists.freedesktop.org/msg18788.html
> Cc: Jani Nikula <jani.nikula@intel.com>
> Cc: Takashi Iwai <tiwai@suse.de>
> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>

Well, although I fully agree that it's better to clear all voodoo once
and fix from scratch, my concern is that it'll cause mess for stable
kernel.  This path won't fix anything by itself, so it's not suitable
for stable alone.  If any, it should be together with the real fix
patch.

I guess you'll submit the proper fix patch(es) to stable later on?


thanks,

Takashi

> ---
>  drivers/gpu/drm/i915/intel_panel.c |   10 +---------
>  1 file changed, 1 insertion(+), 9 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/intel_panel.c b/drivers/gpu/drm/i915/intel_panel.c
> index a3730e0..f31064a 100644
> --- a/drivers/gpu/drm/i915/intel_panel.c
> +++ b/drivers/gpu/drm/i915/intel_panel.c
> @@ -336,7 +336,7 @@ void intel_panel_enable_backlight(struct drm_device *dev,
>  		 * we don't track the backlight dpms state, hence check whether
>  		 * we have to do anything first. */
>  		if (tmp & BLM_PWM_ENABLE)
> -			goto set_level;
> +			return;
>  
>  		if (dev_priv->num_pipe == 3)
>  			tmp &= ~BLM_PIPE_SELECT_IVB;
> @@ -357,14 +357,6 @@ void intel_panel_enable_backlight(struct drm_device *dev,
>  			I915_WRITE(BLC_PWM_PCH_CTL1, tmp);
>  		}
>  	}
> -
> -set_level:
> -	/* Check the current backlight level and try to set again if it's zero.
> -	 * On some machines, BLC_PWM_CPU_CTL is cleared to zero automatically
> -	 * when BLC_PWM_CPU_CTL2 and BLC_PWM_PCH_CTL1 are written.
> -	 */
> -	if (!intel_panel_get_backlight(dev))
> -		intel_panel_actually_set_backlight(dev, dev_priv->backlight_level);
>  }
>  
>  static void intel_panel_init_backlight(struct drm_device *dev)
> -- 
> 1.7.10.4
> 

  reply	other threads:[~2013-03-22 10:00 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-22  9:53 [PATCH 1/3] Revert "drm/i915: dynamic Haswell display power well support" Daniel Vetter
2013-03-22  9:53 ` [PATCH 2/3] Revert "drm/i915: set TRANSCODER_EDP even earlier" Daniel Vetter
2013-03-22 12:30   ` Paulo Zanoni
2013-03-22 13:59     ` Daniel Vetter
2013-03-22 13:43   ` Daniel Vetter
2013-03-22  9:53 ` [PATCH 3/3] drm/i915: Revert backlight cargo-culting Daniel Vetter
2013-03-22 10:00   ` Takashi Iwai [this message]
2013-03-22 10:13     ` Daniel Vetter
2013-03-22 10:22       ` Daniel Vetter
2013-03-22 10:42         ` Takashi Iwai
2013-03-22 11:22           ` Daniel Vetter
2013-03-22 11:34             ` Takashi Iwai
2013-03-22 14:01               ` Daniel Vetter
2013-03-22 14:44                 ` [PATCH] Revert "drm/i915: write backlight harder" Daniel Vetter
2013-03-22 15:06                   ` Takashi Iwai
2013-03-23 11:36                     ` Daniel Vetter
2013-03-22 14:45 ` [PATCH 1/7] drm/i915: don't disable the power well yet Paulo Zanoni
2013-03-22 15:22   ` Daniel Vetter
2013-03-22 17:07     ` Paulo Zanoni
2013-03-23 11:34       ` Daniel Vetter

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=s5h38vnbvpz.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=daniel.vetter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox