From: Kristen Accardi <kristen.c.accardi@intel.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-kernel@vger.kernel.org, greg@kroah.com,
pcihpd-discuss@lists.sourceforge.net, len.brown@intel.com,
linux-acpi@vger.kernel.org
Subject: Re: [Pcihpd-discuss] Re: [patch 0/4] Hot Dock/Undock support
Date: Wed, 18 Jan 2006 16:06:59 -0800 [thread overview]
Message-ID: <1137629220.31839.56.camel@whizzy> (raw)
In-Reply-To: <20060118222348.GG1580@elf.ucw.cz>
On Wed, 2006-01-18 at 23:23 +0100, Pavel Machek wrote:
<snip>
> Device GDCK looks like dock to my untrained eye. Unfortunately its
> type is IBM0079... ...
>
> Ahha, and ibm_acpi.c agrees with me.
>
> IBM_HANDLE(dock, root, "\\_SB.GDCK", /* X30, X31, X40 */
>
> Scope (\_SB)
> {
> Device (GDCK)
> {
> Name (_HID, EisaId ("IBM0079"))
> Name (_CID, 0x150CD041)
> Method (_STA, 0, NotSerialized)
> {
> ...
> Method (_DCK, 1, NotSerialized)
> {
> Store (0x00, Local0)
> If (LEqual (GGID (), 0x03))
> {
> Store (\_SB.PCI0.LPC.EC.SDCK (Arg0), Local0)
> }
>
> If (LEqual (GGID (), 0x00))
> {
> Store (\_SB.PCI0.PCI1.DOCK.DDCK (Arg0), Local0)
> }
>
> Return (Local0)
> }
>
> Method (_EJ0, 1, NotSerialized)
> {
> If (LEqual (GGID (), 0x03))
> {
> \_SB.PCI0.LPC.EC.SEJ0 (Arg0)
> }
>
> If (LEqual (GGID (), 0x00))
> {
> \_SB.PCI0.PCI1.DOCK.DEJ0 (Arg0)
> }
> }
> ....
>
> Hope this helps.
> Pavel
so the problem that I see is that this dsdt defines two separate dock
devices, one outside the scope of pci, and one within it. The one
outside the scope of pci defines the _EJ0 and _DCK methods. So, when
acpiphp loads, it scans the pci slots for ejectable slots, finds none
(because _EJ0 is defined in the dock device that is outside the scope of
pci) and exits. This dsdt is different from the others I've used in
that most of them define all methods related to docking under the actual
dock bridge (within the scope of pci). perhaps some acpi people can
shed some light on the best way to handle this - otherwise I'm sure I
can hack something up that will be less than acceptable :).
next prev parent reply other threads:[~2006-01-19 0:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 0:56 [patch 0/4] Hot Dock/Undock support Kristen Accardi
2006-01-18 12:16 ` Pavel Machek
2006-01-18 13:04 ` Pavel Machek
2006-01-18 18:42 ` [Pcihpd-discuss] " Kristen Accardi
2006-01-18 19:45 ` Pavel Machek
2006-01-18 21:06 ` Kristen Accardi
2006-01-18 21:47 ` Matthew Garrett
2006-01-18 22:08 ` Pavel Machek
2006-01-18 22:23 ` Pavel Machek
2006-01-19 0:06 ` Kristen Accardi [this message]
2006-01-19 15:23 ` Dmitry Torokhov
2006-01-18 14:51 ` Pavel Machek
2006-01-20 1:27 ` Kristen Accardi
2006-01-18 20:42 ` Pavel Machek
2006-01-18 21:43 ` Kristen Accardi
2006-01-18 21:11 ` Pavel Machek
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=1137629220.31839.56.camel@whizzy \
--to=kristen.c.accardi@intel.com \
--cc=greg@kroah.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=pcihpd-discuss@lists.sourceforge.net \
/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