From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Pauli Nieminen <suokkos@gmail.com>
Cc: Paul Mundt <lethal@linux-sh.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Luca Tettamanti <kronos.it@gmail.com>,
Linux PCI <linux-pci@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
pm list <linux-pm@lists.linux-foundation.org>,
dri-devel@lists.sourceforge.net
Subject: Re: [Q] How to tell we're using the KMS (during suspend/resume) outside the graphics driver
Date: Wed, 10 Mar 2010 20:56:18 +0000 [thread overview]
Message-ID: <20100310205618.GA28628@srcf.ucam.org> (raw)
In-Reply-To: <548cdfc21003100254t5c94aca5u5cf1e9eb29215325@mail.gmail.com>
As far as the ACPI video driver goes, acpi_get_physical_pci_device()
will give you something to work with. 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.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2010-03-10 20:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-06 21:36 [Q] How to tell we're using the KMS (during suspend/resume) outside the graphics driver Rafael J. Wysocki
2010-03-09 11:01 ` Luca Tettamanti
2010-03-09 11:34 ` Rafael J. Wysocki
2010-03-09 11:38 ` Rafał Miłecki
2010-03-09 16:16 ` James Simmons
2010-03-09 21:08 ` Rafael J. Wysocki
2010-03-10 5:50 ` Paul Mundt
2010-03-10 10:54 ` Pauli Nieminen
2010-03-10 20:56 ` Matthew Garrett [this message]
2010-03-10 21:15 ` Rafael J. Wysocki
2010-03-10 21:17 ` Matthew Garrett
2010-04-06 7:47 ` Rafał Miłecki
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=20100310205618.GA28628@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=dri-devel@lists.sourceforge.net \
--cc=jbarnes@virtuousgeek.org \
--cc=kronos.it@gmail.com \
--cc=lethal@linux-sh.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=rjw@sisk.pl \
--cc=suokkos@gmail.com \
/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