From: Lekensteyn <lekensteyn@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org,
Sergio Perez <dagobertstaler@gmail.com>,
"Moore, Robert" <robert.moore@intel.com>
Subject: Re: [PATCH] ACPI: return first _ADR match for acpi_get_child
Date: Wed, 26 Dec 2012 16:15:16 +0100 [thread overview]
Message-ID: <1985295.2rJ73b5T91@al> (raw)
In-Reply-To: <2952714.u8moKLOMiJ@vostro.rjw.lan>
On Wednesday 26 December 2012 15:13:00 Rafael J. Wysocki wrote:
> But as far as I can say, there also are _PS0, _PS1 and _PS3 methods under
> PEG0.VGA and there are display devices under it.
_PS0, _PS1 and _PS3 just set _PSC for ACPI. It does interact with any
hardware. The display adapter use "CADL" (\CADL based on the scope of
CRT._DCS, not to be confused with \_SB.PCI0.GFX0.CADL (field IGDM)). This field
is only written in NVIF. It seems to be a display adapter used for a nvidia
graphics card.
I know that some Lenovo laptops allow you to select Intel / Nvidia / Optimus
in their BIOS, maybe this PEG0.VGA is used for the nvidia-only setup (lazy
Lenovo engineers?). Note that this does *not* apply to this IdeaPad Y570 or a
Lenovo IdeaPad Y470, these laptops force you into the Optimus mode which means
that you have two graphics cards activated.
> Moreover, it seems to have
> _DOS defined (which PEGP doesn't have), so I'm not really sure we should
> prefer PEG0.PEGP to PEG0.VGA after all?
The code is a subset of what \_SB.PCI0.GFX0._DOS does.
VGA._DOS:
Store (And (Arg0, 0x07), DSEN)
GFX0._DOS:
Store (And (Arg0, 0x07), DSEN)
If (LEqual (And (Arg0, 0x03), Zero)) {
If (CondRefOf (HDOS)) {
HDOS ()
}
}
> I wonder what PEG0.PEGP and PEG0.VGA are supposed to represent, actually.
PEGP represents the more powerful Nvidia graphics card. GFX0 is the more
power-aggressive Intel graphics card. VGA... is something useless? A "it
works, do not touch anything" leftover? There is also a completely useless
VGA1 device. To quote Linus [1]:
> It's that simple. Don't expect anything else. Firmware is written by
> people who have lost the will to live (why? Because they do firmware
> development for a living), and the only thing keeping them going is
> the drugs. And they're not the "fun" kind of drugs. The end result is
> predictable. In their drug-induced haze, they make a mess.
Regards,
Peter
[1]: http://lkml.org/lkml/2012/10/21/75
prev parent reply other threads:[~2012-12-26 15:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 22:28 [PATCH] ACPI: return first _ADR match for acpi_get_child Lekensteyn
2012-11-16 16:25 ` Len Brown
2012-11-16 18:37 ` Lekensteyn
2012-12-19 11:31 ` Rafael J. Wysocki
2012-12-19 22:40 ` Lekensteyn
2012-12-26 14:13 ` Rafael J. Wysocki
2012-12-26 15:15 ` Lekensteyn [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=1985295.2rJ73b5T91@al \
--to=lekensteyn@gmail.com \
--cc=dagobertstaler@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=robert.moore@intel.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;
as well as URLs for NNTP newsgroup(s).