public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Shaohua Li <shaohua.li@intel.com>
To: Holger Macht <hmacht@suse.de>
Cc: linux acpi <linux-acpi@vger.kernel.org>,
	Len Brown <lenb@kernel.org>, Andi Kleen <andi@firstfloor.org>,
	Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
	mjg59 <mjg59@srcf.ucam.org>, Tejun Heo <htejun@gmail.com>
Subject: Re: [patch 1/11]avoid check _STA method
Date: Wed, 24 Sep 2008 10:51:05 +0800	[thread overview]
Message-ID: <1222224665.968.3.camel@sli10-desk.sh.intel.com> (raw)
In-Reply-To: <20080922105759.GB26633@homac.suse.de>

On Mon, 2008-09-22 at 18:57 +0800, Holger Macht wrote:
> On Thu 28. Aug - 10:02:03, Shaohua Li wrote:
> > In some BIOSes, every _STA method call will send a notification again,
> > this cause freeze. And in some BIOSes, it appears _STA should be called
> > after _DCK. This tries to avoid calls _STA, and still keep the device
> > present check.
> > http://bugzilla.kernel.org/show_bug.cgi?id=10431
> 
> Finally found some time to test this...
> 
> >
> > Signed-off-by: Shaohua Li <shaohua.li@intel.com>
> > ---
> >  drivers/acpi/dock.c |    5 ++++-
> >  1 file changed, 4 insertions(+), 1 deletion(-)
> >
> > Index: linux/drivers/acpi/dock.c
> > ===================================================================
> > --- linux.orig/drivers/acpi/dock.c    2008-08-27 14:38:44.000000000 +0800
> > +++ linux/drivers/acpi/dock.c 2008-08-28 09:33:02.000000000 +0800
> > @@ -604,14 +604,17 @@ static int handle_eject_request(struct d
> >  static void dock_notify(acpi_handle handle, u32 event, void *data)
> >  {
> >       struct dock_station *ds = data;
> > +     struct acpi_device *tmp;
> >
> >       switch (event) {
> >       case ACPI_NOTIFY_BUS_CHECK:
> > -             if (!dock_in_progress(ds) && dock_present(ds)) {
> > +             if (!dock_in_progress(ds) && acpi_bus_get_device(ds->handle,
> 
> On the Thinkpad X60, when booting undocked, the first time I dock,
> acpi_bus_get_device() returns 0, so hotplug is not performed
> properly. Second time (undock->dock), it works.
So the patch breaks your X60? acpi_bus_get_device() returns 0 means the
device is already in ACPI device tree, but it shouldn't as it's not
present.

Thanks,
Shaohua


  reply	other threads:[~2008-09-24  2:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-28  2:02 [patch 1/11]avoid check _STA method Shaohua Li
2008-08-29 15:19 ` Thomas Renninger
2008-09-22 10:57 ` Holger Macht
2008-09-24  2:51   ` Shaohua Li [this message]
2008-09-24 12:17     ` Holger Macht
2008-09-25 14:49     ` Holger Macht
2008-09-26  1:04       ` Shaohua Li
2008-11-11 12:17         ` Holger Macht
2008-09-24  3:38 ` Len Brown
  -- strict thread matches above, loose matches on Subject: below --
2008-08-27  3:14 Shaohua Li
2008-08-27  7:53 ` Andi Kleen
2008-08-27  8:24   ` Li, Shaohua
2008-08-27  8:56     ` Andi Kleen
2008-08-27  8:57       ` Alan Jenkins

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=1222224665.968.3.camel@sli10-desk.sh.intel.com \
    --to=shaohua.li@intel.com \
    --cc=andi@firstfloor.org \
    --cc=hmacht@suse.de \
    --cc=hmh@hmh.eng.br \
    --cc=htejun@gmail.com \
    --cc=lenb@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox