From: Alex Williamson <alex.williamson-VXdhtT5mjnY@public.gmane.org>
To: Paul Ionescu <i_p_a_u_l-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [RFC] filling in ACPI files in sysfs
Date: Thu, 08 Apr 2004 08:36:59 -0600 [thread overview]
Message-ID: <1081435019.2745.21.camel@patsy.fc.hp.com> (raw)
In-Reply-To: <20040408081455.52935.qmail-BuYeCebq3BaA/QwVtaZbd3CJp6faPEW9@public.gmane.org>
On Thu, 2004-04-08 at 02:14, Paul Ionescu wrote:
> Hi Alex,
>
> I attached a file containing what I have in
> /sys/firmware/acpi with your second patch.
Thanks, looks like your namespace is more complete than on my old
omnibook.
> I also tried the docking station with:
> echo 1 >
> /sys/firmware/acpi/namespace/ACPI/_SB/PCI0/PCI1/DOCK/_DCK
>
> and
>
> echo 0 >
> /sys/firmware/acpi/namespace/ACPI/_SB/PCI0/PCI1/DOCK/_DCK
>
> with this commands I semi turned on/off the doking
> station. I say semi because is not fully on/off.
> When I turn it on (echo 1 > _DCK), the docking station
> fan starts, and the LED indicating the usage of
> docking station turns on, but I dont see the new
> devices from the docking station (2 new usb, 2 new
> cardbus, 1 new ide, 1 new pci etc). I suspect this is
> not your patch fault, but the way ACPI handles this
> event. It should add the new description tables of
> ACPI devices on the fly not only at boot time. When it
> boots without docking station ACPI has no way to know
> what will be in my docking station, so it has to add
> new devices after inserting and activating the
> docking.
Yes, as far as I'm aware, we don't try to re-parse acpi namespace
after such events. I'm not trying to solve that problem though. This
is also just a raw interface to the acpi methods, so undocking w/o
handling the things that will get removed may be unsafe. I envision it
being an interface by which hotplug could evaluate, via the _EJD
methods, what devices will go away and do smart things prior to the
actual eject. On my docking station, there's no obvious effect of
calling the _DCK method, but calling _EJ0 pops it out. Also, I see all
3 possible batteries under /proc/acpi/battery (even though only 1 is
plugged in), so I doubt this patch is changing that behavior at all.
> Now, when I turn it off (with echo 0 > _DCK), the fan
> stops, but the ACTIVE led is still on, and the
> electromechanical eject was not activated.
>
> Is this the way I was supposed to test docking ?
Try the _EJ0 method. Assuming all device that you'll lose are
quiesced and removed (probably everything that lists _SB.PCI0.PCI1.DOCK
in their _EJD method), I believe you need to do the following sequence:
echo 0 > _DCK
echo 1 > _EJ0
And after you re-dock, you should probably echo 1 > _DCK. Thanks,
Alex
--
Alex Williamson HP Linux & Open Source Lab
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
next prev parent reply other threads:[~2004-04-08 14:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-08 8:14 [RFC] filling in ACPI files in sysfs Paul Ionescu
[not found] ` <20040408081455.52935.qmail-BuYeCebq3BaA/QwVtaZbd3CJp6faPEW9@public.gmane.org>
2004-04-08 14:36 ` Alex Williamson [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-07 21:36 Paul Ionescu
[not found] ` <1081373781.23176.30.camel-LjAuIDrFwz0@public.gmane.org>
2004-04-07 22:13 ` Alex Williamson
[not found] ` <1081376023.2748.15.camel-Wmjt7DDUnIVxnVILBQAtiA@public.gmane.org>
2004-04-08 5:56 ` Paul Ionescu
2004-04-08 15:46 ` Paul Ionescu
[not found] ` <1081439217.23176.70.camel-LjAuIDrFwz0@public.gmane.org>
2004-04-08 16:41 ` Alex Williamson
2004-04-08 16:53 ` Paul Ionescu
2004-04-08 17:25 ` Matthew Wilcox
[not found] ` <20040408172548.GH18329-+pPCBgu9SkPzIGdyhVEDUDl5KyyQGfY2kSSpQ9I8OhVaa/9Udqfwiw@public.gmane.org>
2004-04-08 17:33 ` Alex Williamson
[not found] ` <1081536801.26073.120.camel@t40>
[not found] ` <1081537175.2694.11.camel@patsy.fc.hp.com>
[not found] ` <1081537175.2694.11.camel-Wmjt7DDUnIVxnVILBQAtiA@public.gmane.org>
2004-04-10 10:03 ` Paul Ionescu
[not found] ` <1081536489.23178.113.camel@t40>
[not found] ` <1081537087.2694.8.camel@patsy.fc.hp.com>
[not found] ` <1081537087.2694.8.camel-Wmjt7DDUnIVxnVILBQAtiA@public.gmane.org>
2004-04-10 11:36 ` Paul Ionescu
2004-04-06 15:56 Alex Williamson
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=1081435019.2745.21.camel@patsy.fc.hp.com \
--to=alex.williamson-vxdhtt5mjny@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=i_p_a_u_l-/E1597aS9LQAvxtiuMwx3w@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox