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, 19 Dec 2012 23:40:47 +0100 [thread overview]
Message-ID: <4931572.xMaToDeW2Z@al> (raw)
In-Reply-To: <2271508.zSFZF7r2W9@vostro.rjw.lan>
Hi,
On Wednesday 19 December 2012 12:31:35 Rafael J. Wysocki wrote:
> > This is a well-aimed shot in the dark based on the DSDT I see.
>
> Can you post that DSDT by chance?
The DSDT for a Lenovo Ideapad Y470 has been posted before to
https://bugzilla.kernel.org/show_bug.cgi?id=42696.
>From dsdt.dsl,
line 9279 (context Device(\_SB.PCI0.PEG0)):
Name (_ADR, 0x00010000)
line 9377 (context Device(\_SB.PCI0.PEG0.PEGP)):
Name (_ADR, 0xFFFF)
line 9414 (context Device(\_SB.PCI0.PEG0.VGA)):
Name (_ADR, Zero)
>From ssdt6.dsl, line 1070, (context Device(\_SB.PCI0.PEG0.PEGP)):
Method (_INI, 0, NotSerialized)
{
Store (Zero, \_SB.PCI0.PEG0.PEGP._ADR)
}
> > It is certainly
> > not a solid proof that is won't break other machines and if it does break.
> > As far as PCI is concerned, it only affects machines with multiple
> > handles that have the same PCI address returned by _ADR.
>
> I wonder if there are any other criteria we can use to choose the "best"
> handle in those cases? It doesn't look like choosing the first on or the
> last one is really going to always work.
Currently I do not have other ideas to get this to work, but Intel may have an
ACPI expert who can help out here based on experience.
Regards,
Peter
next prev parent reply other threads:[~2012-12-19 22:41 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 [this message]
2012-12-26 14:13 ` Rafael J. Wysocki
2012-12-26 15:15 ` Lekensteyn
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=4931572.xMaToDeW2Z@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).