From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: "ACPI Devel Maling List" <linux-acpi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"Linux PCI" <linux-pci@vger.kernel.org>,
"Mike Lothian" <mike@fireburn.co.uk>,
madcatx@atlas.cz, "Alex Deucher" <alexdeucher@gmail.com>,
"Dave Airlie" <airlied@linux.ie>, "Takashi Iwai" <tiwai@suse.de>,
"Joaquín Aramendía" <samsagax@gmail.com>
Subject: Re: [PATCH][update] ACPIPHP / radeon / nouveau: Fix VGA switcheroo problem related to hotplug events
Date: Mon, 30 Dec 2013 11:20:43 +0200 [thread overview]
Message-ID: <20131230092043.GB2494@intel.com> (raw)
In-Reply-To: <3135179.iXEx1Rk87m@vostro.rjw.lan>
On Sun, Dec 29, 2013 at 10:36:56PM +0100, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>
> The changes in the ACPI-based PCI hotplug (ACPIPHP) subsystem made
> during the 3.12 development cycle uncovered a problem with VGA
> switcheroo that on some systems, when the device-specific method
> (ATPX in the radeon case, _DSM in the nouveau case) is used to turn
> off the discrete graphics, the BIOS generates ACPI hotplug events for
> that device and those events cause ACPIPHP to attempt to remove the
> device from the system (they are events for a device that was present
> previously and is not present any more, so that's what should be done
> according to the spec). Then, the system stops functioning correctly.
>
> Since the hotplug events in question were simply silently ignored
> previously, the least intrusive way to address that problem is to
> make ACPIPHP ignore them again. For this purpose, introduce a new
> ACPI device flag, no_hotplug, and modify ACPIPHP to ignore hotplug
> events for PCI devices whose ACPI companions have that flag set.
> Next, make the radeon and nouveau switcheroo detection code set the
> no_hotplug flag for the discrete graphics' ACPI companion.
>
> Fixes: bbd34fcdd1b2 (ACPI / hotplug / PCI: Register all devices under the given bridge)
> References: https://bugzilla.kernel.org/show_bug.cgi?id=61891
> References: https://bugzilla.kernel.org/show_bug.cgi?id=64891
> Reported-and-tested-by: Mike Lothian <mike@fireburn.co.uk>
> Reported-and-tested-by: <madcatx@atlas.cz>
> Reported-by: Joaquín Aramendía <samsagax@gmail.com>
> Cc: Alex Deucher <alexdeucher@gmail.com>
> Cc: Dave Airlie <airlied@linux.ie>
> Cc: Takashi Iwai <tiwai@suse.de>
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> Cc: 3.12+ <stable@vger.kernel.org> # 3.12+
FWIW, Thunderbolt hotplug still works fine after this patch is applied :)
next prev parent reply other threads:[~2013-12-30 9:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-28 22:13 [PATCH] ACPIPHP / radeon: Fix VGA switcheroo problem related to hotplug events Rafael J. Wysocki
2013-12-29 21:36 ` [PATCH][update] ACPIPHP / radeon / nouveau: " Rafael J. Wysocki
2013-12-30 9:20 ` Mika Westerberg [this message]
2013-12-30 12:52 ` Rafael J. Wysocki
2013-12-31 21:14 ` [PATCH][update 2] ACPIPHP / radeon / nouveau: Fix VGA switcheroo problem related to hotplug Rafael J. Wysocki
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=20131230092043.GB2494@intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=airlied@linux.ie \
--cc=alexdeucher@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=madcatx@atlas.cz \
--cc=mike@fireburn.co.uk \
--cc=rjw@rjwysocki.net \
--cc=samsagax@gmail.com \
--cc=tiwai@suse.de \
/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