From: Mario Limonciello <mario_limonciello@dell.com>
To: Matthew Garrett <matthew.garrett@nebula.com>
Cc: "platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>
Subject: Re: [PATCH v3 0/1] alienware-wmi: Update HDMI control methods
Date: Wed, 26 Feb 2014 18:16:55 -0600 [thread overview]
Message-ID: <530E83F7.5060801@dell.com> (raw)
In-Reply-To: <1393459426.14900.56.camel@x230>
On 02/26/2014 06:03 PM, Matthew Garrett wrote
> Could you clarify what the HDMI mux is for? Is there any method in the
> HDMI WMI call to determine whether it's supported rather than relying on
> DMI? (I appreciate that in this kind of case there may not be)
>
The HDMI mux will control what's displayed on the HDMI output port. It can toggle between an HDMI input device and the system's standard video output.
Since the same GUID and WMI method are used both on platforms that support HDMI mux as well as platforms that support just lighting control I don't think it will be possible to determine if it's supported. You could possibly make a WMI call and attempting to toggle or query, however the behavior is undefined for those arguments on firmware for other systems. While I was initially putting this driver together I made mistakes with the arguments early on that caused very colorful corruption all over the display, so I think it would be better to restrict it by DMI data if possible.
prev parent reply other threads:[~2014-02-27 0:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 23:47 [PATCH v3 0/1] alienware-wmi: Update HDMI control methods Mario Limonciello
2014-02-26 23:47 ` [PATCH v3 1/1] Add WMI driver for controlling AlienFX and HDMI on Alienware Mario Limonciello
2014-02-27 0:03 ` [PATCH v3 0/1] alienware-wmi: Update HDMI control methods Matthew Garrett
2014-02-27 0:16 ` Mario Limonciello [this message]
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=530E83F7.5060801@dell.com \
--to=mario_limonciello@dell.com \
--cc=matthew.garrett@nebula.com \
--cc=platform-driver-x86@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.