From patchwork Fri Jul 5 22:23:26 2013 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Rafael Wysocki X-Patchwork-Id: 2824390 Return-Path: X-Original-To: patchwork-linux-acpi@patchwork.kernel.org Delivered-To: patchwork-parsemail@patchwork1.web.kernel.org Received: from mail.kernel.org (mail.kernel.org [198.145.19.201]) by patchwork1.web.kernel.org (Postfix) with ESMTP id CD0339F3EB for ; Fri, 5 Jul 2013 22:13:50 +0000 (UTC) Received: from mail.kernel.org (localhost [127.0.0.1]) by mail.kernel.org (Postfix) with ESMTP id EC68020157 for ; Fri, 5 Jul 2013 22:13:49 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 32B5F2014E for ; Fri, 5 Jul 2013 22:13:48 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751236Ab3GEWNr (ORCPT ); Fri, 5 Jul 2013 18:13:47 -0400 Received: from hydra.sisk.pl ([212.160.235.94]:59867 "EHLO hydra.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751018Ab3GEWNq (ORCPT ); Fri, 5 Jul 2013 18:13:46 -0400 Received: from vostro.rjw.lan (cmk108.neoplus.adsl.tpnet.pl [83.31.138.108]) by hydra.sisk.pl (Postfix) with ESMTPSA id C7D85E3DC7; Sat, 6 Jul 2013 00:09:43 +0200 (CEST) From: "Rafael J. Wysocki" To: Matthew Garrett Cc: daniel.vetter@ffwll.ch, linux-acpi@vger.kernel.org, seth.forshee@canonical.com, joeyli.kernel@gmail.com, intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, lenb@kernel.org Subject: Re: [PATCH 3/3] i915: Don't provide ACPI backlight interface if firmware expects Windows 8 Date: Sat, 06 Jul 2013 00:23:26 +0200 Message-ID: <2962350.laXfENfrac@vostro.rjw.lan> User-Agent: KMail/4.9.5 (Linux/3.10.0+; KDE/4.9.5; x86_64; ; ) In-Reply-To: <2888060.4Smt6Tu6bv@vostro.rjw.lan> References: <1370818899-8595-1-git-send-email-matthew.garrett@nebula.com> <2759570.WXymCRumvH@vostro.rjw.lan> <2888060.4Smt6Tu6bv@vostro.rjw.lan> MIME-Version: 1.0 Sender: linux-acpi-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-acpi@vger.kernel.org X-Spam-Status: No, score=-7.1 required=5.0 tests=BAYES_00, RCVD_IN_DNSWL_HI, RP_MATCHES_RCVD, UNPARSEABLE_RELAY autolearn=unavailable version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mail.kernel.org X-Virus-Scanned: ClamAV using ClamSMTP On Friday, July 05, 2013 11:40:02 PM Rafael J. Wysocki wrote: > On Friday, July 05, 2013 10:00:55 PM Rafael J. Wysocki wrote: > > On Friday, July 05, 2013 02:20:14 PM Rafael J. Wysocki wrote: > > > On Sunday, June 09, 2013 07:01:39 PM Matthew Garrett wrote: > > > > Windows 8 leaves backlight control up to individual graphics drivers rather > > > > than making ACPI calls itself. There's plenty of evidence to suggest that > > > > the Intel driver for Windows doesn't use the ACPI interface, including the > > > > fact that it's broken on a bunch of machines when the OS claims to support > > > > Windows 8. The simplest thing to do appears to be to disable the ACPI > > > > backlight interface on these systems. > > > > > > > > Signed-off-by: Matthew Garrett > > > > --- > > > > drivers/gpu/drm/i915/i915_dma.c | 3 +++ > > > > 1 file changed, 3 insertions(+) > > > > > > > > diff --git a/drivers/gpu/drm/i915/i915_dma.c b/drivers/gpu/drm/i915/i915_dma.c > > > > index 3b315ba..23b6292 100644 > > > > --- a/drivers/gpu/drm/i915/i915_dma.c > > > > +++ b/drivers/gpu/drm/i915/i915_dma.c > > > > @@ -1661,6 +1661,9 @@ int i915_driver_load(struct drm_device *dev, unsigned long flags) > > > > /* Must be done after probing outputs */ > > > > intel_opregion_init(dev); > > > > acpi_video_register(); > > > > + /* Don't use ACPI backlight functions on Windows 8 platforms */ > > > > + if (acpi_osi_version() >= ACPI_OSI_WIN_8) > > > > + acpi_video_backlight_unregister(); > > > > } > > > > > > > > if (IS_GEN5(dev)) > > > > > > > > > > Well, this causes build failures to happen when the ACPI video driver is > > > modular and the graphics driver is not. > > > > > > I'm not sure how to resolve that, so suggestions are welcome. > > > > Actually, that happened with the radeon patch. > > > > That said, ACPI_OSI_WIN_8 doesn't make much sense for !CONFIG_ACPI, for > > example. > > > > What about making acpi_video_register() do the quirk instead? We could add an > > argument to it indicating whether or not quirks should be applied. > > Actually, I wonder what about the appended patch (on top of the Aaron's > https://patchwork.kernel.org/patch/2812951/) instead of [1-3/3] from this series. Or even something as simple as this one. --- drivers/acpi/video_detect.c | 3 +++ 1 file changed, 3 insertions(+) -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Index: linux-pm/drivers/acpi/video_detect.c =================================================================== --- linux-pm.orig/drivers/acpi/video_detect.c +++ linux-pm/drivers/acpi/video_detect.c @@ -203,6 +203,9 @@ long acpi_video_get_capabilities(acpi_ha */ dmi_check_system(video_detect_dmi_table); + + if (acpi_gbl_osi_data >= ACPI_OSI_WIN_8) + acpi_video_support |= ACPI_VIDEO_BACKLIGHT_FORCE_VENDOR; } else { status = acpi_bus_get_device(graphics_handle, &tmp_dev); if (ACPI_FAILURE(status)) {