From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Terence Ripperda <tripperda@nvidia.com>
Cc: Zhang Rui <rui.zhang@intel.com>,
"lenb@kernel.org" <lenb@kernel.org>,
linux-acpi <linux-acpi@vger.kernel.org>
Subject: Re: patch for video.c driver
Date: Fri, 13 Mar 2009 20:52:56 +0000 [thread overview]
Message-ID: <20090313205256.GA5854@srcf.ucam.org> (raw)
In-Reply-To: <20090313204544.GR16754@hygelac>
On Fri, Mar 13, 2009 at 03:45:44PM -0500, Terence Ripperda wrote:
> NVIF methods implement both notification and query commands. so it's required
> for generating the event and querying the firmware's preferred set of enabled
> outputs.
Ok, got you. In that case the best approach would be for you to add an
input device to the kernel component of your driver which listens for
the notification and then generates KEY_SWITCHVIDEOMODE. The right level
of integration for the preferred set of screens would be to extend the
video output class to support listing the outputs as well as just
performing the switches, then register with that if the platform doesn't
support DGS and co. We're trying to deprecate the proc interfaces, and
in general platform-specific drivers should hook into generic interfaces
rather than overloading the functionality of the existing ACPI drivers.
Do you have any examples of machines that have this requirement?
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2009-03-13 20:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090312154741.GA1055@hygelac>
2009-03-13 2:08 ` patch for video.c driver Zhang Rui
2009-03-13 3:00 ` Matthew Garrett
2009-03-13 17:11 ` Rafael J. Wysocki
2009-03-13 17:36 ` Terence Ripperda
2009-03-13 17:47 ` Matthew Garrett
2009-03-13 17:58 ` Terence Ripperda
2009-03-13 18:06 ` Matthew Garrett
2009-03-13 20:45 ` Terence Ripperda
2009-03-13 20:52 ` Matthew Garrett [this message]
2009-03-14 7:55 ` Len Brown
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=20090313205256.GA5854@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=tripperda@nvidia.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