From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
Linux PCI <linux-pci@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: [Q] How to tell we're using the KMS (during suspend/resume) outside the graphics driver
Date: Sat, 6 Mar 2010 22:36:09 +0100 [thread overview]
Message-ID: <201003062236.09801.rjw@sisk.pl> (raw)
Hi,
For at least two reasons it would be beneficial for some code outisde the
graphics driver(s) to know if the KMS are used.
First, in the non-KMS (ie. UMS) case we probably wouldn't want to call
acpi_video_resume(), because that has a potential to mess up with the GPU
(it actually is known to do that on at least one system).
Second, in the KMS case, we'd be able to skip the kernel VT switch, because
the KMS driver uses its own framebuffer anyway.
So, is there any reasonable way to check that from the outside of the graphics
driver? It should be general enough to cover the cases when there are two
graphics adapters with different drivers in the system and so forth.
Rafael
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--
next reply other threads:[~2010-03-06 21:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-06 21:36 Rafael J. Wysocki [this message]
2010-03-09 11:01 ` [Q] How to tell we're using the KMS (during suspend/resume) outside the graphics driver 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
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=201003062236.09801.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=dri-devel@lists.sourceforge.net \
--cc=jbarnes@virtuousgeek.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=mjg59@srcf.ucam.org \
/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