From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Rafael J. Wysocki" Subject: Re: [Q] How to tell we're using the KMS (during suspend/resume) outside the graphics driver Date: Wed, 10 Mar 2010 22:15:26 +0100 Message-ID: <201003102215.26232.rjw@sisk.pl> References: <201003062236.09801.rjw@sisk.pl> <548cdfc21003100254t5c94aca5u5cf1e9eb29215325@mail.gmail.com> <20100310205618.GA28628@srcf.ucam.org> Mime-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20100310205618.GA28628@srcf.ucam.org> Sender: linux-pci-owner@vger.kernel.org To: Matthew Garrett Cc: Pauli Nieminen , Paul Mundt , Luca Tettamanti , Linux PCI , LKML , Jesse Barnes , ACPI Devel Maling List , pm list , dri-devel@lists.sourceforge.net List-Id: linux-acpi@vger.kernel.org On Wednesday 10 March 2010, Matthew Garrett wrote: > As far as the ACPI video driver goes, acpi_get_physical_pci_device() > will give you something to work with. Hmm. Did you mean acpi_get_physical_device()? Which acpi_device should I call that for? > For the console-switching case, I think the most reasonable plan is probably > to add a flag to the console drivers to indicate whether or not they support > reprogramming the hardware themselves, and then walk all active console > drivers. There'd need to be a way for fb drivers to tell fbcon that they can > handle it. Yes, that sounds reasonable. Rafael