All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Kristen Carlson Accardi <kristenc@cs.pdx.edu>
Cc: pcihpd-discuss@lists.sourceforge.net, greg@kroah.com,
	len.brown@intel.com, linux-kernel@vger.kernel.org,
	muneda.takahiro@jp.fujitsu.com, linux-acpi@vger.kernel.org
Subject: Re: [patch] acpiphp: handle dock stations
Date: Mon, 6 Feb 2006 14:21:51 +0100	[thread overview]
Message-ID: <20060206132151.GA1655@elf.ucw.cz> (raw)
In-Reply-To: <20060201233005.GA4999@nerpa>

Hi!

> This patch will add hot add/remove of docking stations to acpiphp.  Because
> some docking stations will have a _DCK method that is not associated with
> a dock bridge, we use the _EJD method to determine which devices are 
> dependent on the dock device, then try to find which of these dependent
> devices are pci devices.  We register a separate event handler with acpi
> to handle dock notifications, but if we have discovered any pci devices
> dependent on the dock station, we notify the acpiphp driver to rescan
> the correct bus.  If no pci devices are found, but there is still a _DCK method
> present, the driver will stay loaded to deal with the dock
> notifications.

Even while machine is locked in dock, I don't see aditional devices at
lspci. Is there some additional steps I need to do?

-rw-r--r--  1 root root 4096 Feb  6 14:17 attention

..should probably be write-only. It seems to only return errors on
read, anyway.

Is there a way to physicaly remove my machine from dock? echo 0 >
power should do it, right? Well, it does not :-).

								Pavel
-- 
Web maintainer for suspend.sf.net (www.sf.net/projects/suspend) wanted...

  parent reply	other threads:[~2006-02-06 13:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-01 23:30 [patch] acpiphp: handle dock stations Kristen Carlson Accardi
2006-02-02  5:09 ` [Pcihpd-discuss] " Kenji Kaneshige
2006-02-06 13:15 ` Pavel Machek
2006-02-06 13:21 ` Pavel Machek [this message]
2006-02-13  1:50 ` [Pcihpd-discuss] " MUNEDA Takahiro
2006-02-13 15:57   ` Kenji Kaneshige
2006-02-14  0:41     ` MUNEDA Takahiro

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=20060206132151.GA1655@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=greg@kroah.com \
    --cc=kristenc@cs.pdx.edu \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=muneda.takahiro@jp.fujitsu.com \
    --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 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.