public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Renninger <trenn@suse.de>
To: Shaohua Li <shaohua.li@intel.com>
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>,
	Holger Macht <hmacht@suse.de>, mjg59 <mjg59@srcf.ucam.org>,
	Tejun Heo <htejun@gmail.com>
Subject: Re: [patch 4/11]makeing dock driver supports bay and battery hotplug
Date: Mon, 22 Sep 2008 11:17:42 +0200	[thread overview]
Message-ID: <200809221117.45245.trenn@suse.de> (raw)
In-Reply-To: <1222046694.7241.3.camel@sli10-desk.sh.intel.com>

On Monday 22 September 2008 03:24:54 Shaohua Li wrote:
> On Thu, 2008-09-18 at 13:16 -0600, Thomas Renninger wrote:
> > On Thursday 18 September 2008 19:10:02 Thomas Renninger wrote:
...
> > Above is still valid.
>
> No, this doesn't work. there isn't a acpi_device because battery is
> absent when this is called, but I could add CID support.
I don't know whether there are devices with battery ID in the CID list.
With or without the workaround (rewriting cid checking) it's not perfect.

This is an issue I tried to solve years ago.
Ignoring not present devices is wrong IMO.
The whole current design destroys hotplug integration and results in more
and more workarounds (acpi_memoryhotplug and container driver are nice 
examples).
One has to be careful that only _STA and no other functions are called, but 
not present devices should still get registered in some way and somone (the 
driver itself or maybe better the ACPI subsytem and introduce .notify driver 
ops) should listen on Notify AML calls.
Please tell me if someone looks at this again or has ideas/concerns. I always 
wanted to and will at some point, but still don't have the time.

> > Some of the patches looked like it would be worth for .27, but it's too
> > late now anyway and the problem I hoped it could fix (kacpid utilizes
> > 100% of CPU after suspend, due to _STA -> notify loop) is not solved by
> > these according to Holger.
>
> Yes, this patch set just fixed some bugs. Is there a bugzilla for this
> issue I can look at?
[Bug 401740] kacpi* eat a lot of cpu after s2disk
https://bugzilla.novell.com/show_bug.cgi?id=401740

Thanks,

     Thomas

  reply	other threads:[~2008-09-22  9:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-28  2:03 [patch 4/11]makeing dock driver supports bay and battery hotplug Shaohua Li
2008-09-18 17:10 ` Thomas Renninger
2008-09-18 19:16   ` Thomas Renninger
2008-09-22  1:24     ` Shaohua Li
2008-09-22  9:17       ` Thomas Renninger [this message]
2008-09-22 10:58         ` Holger Macht
  -- strict thread matches above, loose matches on Subject: below --
2008-08-27  3:14 Shaohua Li
2008-08-27 23:13 ` Andi Kleen

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=200809221117.45245.trenn@suse.de \
    --to=trenn@suse.de \
    --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 \
    --cc=shaohua.li@intel.com \
    /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