From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756719Ab1JMSFv (ORCPT ); Thu, 13 Oct 2011 14:05:51 -0400 Received: from cantor2.suse.de ([195.135.220.15]:42807 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756661Ab1JMSFu (ORCPT ); Thu, 13 Oct 2011 14:05:50 -0400 Date: Thu, 13 Oct 2011 20:05:49 +0200 Message-ID: From: Takashi Iwai To: Keith Packard Cc: Chris Wilson , dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] drm/i915/panel: Alwyas record the backlight level again (but cleverly) In-Reply-To: References: User-Agent: Wanderlust/2.15.6 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.7 Emacs/23.3 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org At Thu, 13 Oct 2011 09:40:29 -0700, Keith Packard wrote: > > On Thu, 13 Oct 2011 10:57:35 +0200, Takashi Iwai wrote: > > > This patch fixes the bug by recording the backlight level always > > when changed but only when dev_priv->backlight_enabled is set. > > In this way, the bogus value for disabling backlight can be skipped. > > I think this is better than what we have, but I'm not sure it's quite > what we want -- the backlight level will only be remembered when it is > enabled, so requested changes that happen while the backlight is off > will have no effect. And, requested changes while the panel is disabled > will still go through to the hardware, which can cause problems with > panel power sequencing. > > I think intel_panel_set_backlight should always record the level passed > in, but that intel_panel_disable_backlight and > intel_panel_enable_backlight should use a lower-level function, shared > with intel_panel_set_backlight that doesn't record the value: > > intel_panel_actually_set_backlight(dev, level) { > > } > > intel_panel_set_backlight(dev, level) { > dev_priv->backlight_level = level; > if (dev_priv->backlight_enabled) > intel_panel_actually_set_backlight(dev, level); > } > > intel_panel_enable_backlight(dev) { > dev_priv->backlight_enabled = true; > intel_panel_actually_set_backlight(dev, dev_priv->backlight_level); > } > > intel_panel_disable_backlight(dev) { > dev_priv->backlight_enabled = false; > intel_panel_actually_set_backlight(dev, 0); > } Yes, this looks more understandable, indeed. Would you patch it by yourself or should I refresh the patch? In either way, I'll test tomorrow, as I'm already at home without a test machine. thanks, Takashi