From: Holger Macht <hmacht@suse.de>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: linux-acpi@vger.kernel.org, kristen.c.accardi@intel.com, fseidel@suse.de
Subject: Re: Comments about commit 'PCI: docking station: remove dock uevents'?
Date: Mon, 13 Nov 2006 20:43:27 +0100 [thread overview]
Message-ID: <20061113194326.GD4646@homac2> (raw)
In-Reply-To: <20061113121437.GA18369@srcf.ucam.org>
On Mon 13. Nov - 12:14:37, Matthew Garrett wrote:
> On Sun, Nov 12, 2006 at 03:07:37PM +0100, Holger Macht wrote:
>
> > I'm currently looking at docking station support for various
> > laptops/vendors and what can be done to get them working. At the moment,
> > userspace has to do some quirks to get support for them. For instance,
> > when docking an X60 into a docking station where a SATA DVD drive is
> > located, userland has to rescan the scsi host for the drive to show up.
>
> Does the docking not generate a bus rescan event on the SATA bus? If it
Maybe it does, I'll have to recheck.
> does, it's just a special case of ACPI drive hotplugging. You can't do
> it reliably from userspace, but I think Kirsten has been looking at
> doing it properly in the kernel.
What I'm doing at the moment (for about a week ;-) is to echo "- - -" to
/sys/class/scsi_host/host*/scan for all unoccupied hosts on a dock
event. And this works pretty good. But it's of course only a workaround if
the scsi bus generates an event.
>
> > Additionally, currently the dock driver automatically executes the _DCK
> > method when it detects a dock/undock event. Wouldn't it be good to have
> > common sysfs interface for docking so that userland can trigger the
> > dock/undock? This way userland would also be able to do 'something before'
> > docking/undocking, such as unregistering a device, showing a poput that it
> > is now save to physically undock, etc.
With recent kernel I have to unregister from the drive from userspace to
prevent confusion about if the drive is still there or not.
> When the dock contains a drive, I think there's possibly an argument in
> favour of this. Otherwise, the hardware should be able to deal with it -
> every ACPI-based dock I've played with has had some indication to inform
> the user that the device has disconnected.
Yes, this one has such an indicator, too. I just thought notifying
userspace could be helpful for other cases, that's why I'm asking for
comments.
Thanks,
Holger
next prev parent reply other threads:[~2006-11-13 19:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-12 14:07 Comments about commit 'PCI: docking station: remove dock uevents'? Holger Macht
2006-11-13 12:14 ` Matthew Garrett
2006-11-13 19:43 ` Holger Macht [this message]
2006-11-13 19:50 ` Matthew Garrett
2006-11-13 19:57 ` Holger Macht
2006-11-13 20:18 ` Kristen Carlson Accardi
2006-11-13 19:54 ` Kristen Carlson Accardi
2006-11-13 20:19 ` Holger Macht
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=20061113194326.GD4646@homac2 \
--to=hmacht@suse.de \
--cc=fseidel@suse.de \
--cc=kristen.c.accardi@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=mjg59@srcf.ucam.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.