From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Rafael J. Wysocki" Subject: Re: [PATCH 5/5] acpi_video: Don't handle ACPI brightness notifications by default Date: Fri, 02 Aug 2013 16:41:31 +0200 Message-ID: <1559797.9EdEoD0Bgy@vostro.rjw.lan> References: <20130307193812.GD24233@thinkpad-t410> <1362685180-7768-5-git-send-email-seth.forshee@canonical.com> <51FB49E3.50604@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7Bit Return-path: Received: from hydra.sisk.pl ([212.160.235.94]:52167 "EHLO hydra.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750976Ab3HBObT (ORCPT ); Fri, 2 Aug 2013 10:31:19 -0400 In-Reply-To: <51FB49E3.50604@intel.com> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Aaron Lu Cc: Seth Forshee , Matthew Garrett , linux-acpi@vger.kernel.org, Len Brown , Ben Jencks , joeyli , Micael Dias , * =?ISO-8859-1?Q?SAM=CD?= * , Yves-Alexis Perez On Friday, August 02, 2013 01:55:47 PM Aaron Lu wrote: > On 03/08/2013 03:39 AM, Seth Forshee wrote: > > Windows 8 requires all backlight interfaces to report 101 brightness > > values, and as a result we're starting to see machines with that many > > brightness levels in _BCL. For machines which send these notifications > > when the brightness up/down keys are pressed this means a lot of key > > presses to get any kind of noticeable change in brightness. > > > > For a while now we've had the ability to disable in-kernel handling of > > notifications via the video.brightness_switch_enabled parameter. Change > > this to default to off, and let userspace choose more reasonable > > increments for changing the brightness. > > I just found one more reason for this param to default 0. Do you mean video.brightness_switch_enabled? > We are going to separate the backlight interface control and event > notification functionalities of the ACPI video module, it is highly > possible a lot of systems will use a combination of the event > notification handler and intel_backlight interface. So it doesn't make > sense to let video module to do any adjustment on its own if user space > has chosen a different interface to use. Actually, it can cause problems > as in ASUS's case: > https://bugzilla.kernel.org/show_bug.cgi?id=52951 > > The problem there is, on hotkey brightness up, the video module will > adjust the brightness level first and since its _BQC is broken, it gets > a wrong number(too low or too high or whatever) and then does the _BCM > call. The _BCM method works. Then user space picks the intel_backlight > to do the adjustment, but since the _BCM already sets a wrong value, the > user space's adjustment is affected too. The result is, user has only > two visible levels, very low and very high. > > This only occurs on -rc3, since we removed the > acpi_video_verify_backlight_support from acpi_video_switch_brightness > function. What did we do before -rc2? Did we address that in any way? > So either we make this param default to 0, or we make a new > function to avoid brightness switch in video module for Win8 systems. > > I prefer to set this param to 0 by default. What do you guys think? That depends on what we did earlier. Thanks, Rafael -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center.