mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Li Shaohua <shaohua.li@intel.com>
To: David Brownell <david-b@pacbell.net>
Cc: Dmitry Torokhov <dtor_core@ameritech.net>,
	ACPI-DEV <acpi-devel@lists.sourceforge.net>,
	Len Brown <len.brown@intel.com>, Pavel Machek <pavel@ucw.cz>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [ACPI] RE: PATCH/RFC: driver model/pmcore wakeup hooks (1/4)
Date: Thu, 21 Oct 2004 09:33:28 +0800	[thread overview]
Message-ID: <1098322408.6132.44.camel@sli10-desk.sh.intel.com> (raw)
In-Reply-To: <200410201002.58172.david-b@pacbell.net>

On Thu, 2004-10-21 at 01:02, David Brownell wrote:
> On Tuesday 19 October 2004 20:51, Dmitry Torokhov wrote:
> > On Tuesday 19 October 2004 04:11 am, Li, Shaohua wrote:
> > > A final solution is device core adds an ACPI layer. That is we can
> link
> > > ACPI device and physical device. This way, the PCI device can know
> which
> > > ACPI is linked with it, so the PCI API can use specific ACPI
> method. 
> 
> The driver model core has platform_notify hooks for device add/remove,
> and ACPI should kick in that way ... they might well need tweaks
> though.
The platform_notify information isn't enough to find an ACPI device for
a physical device. To find an ACPI device, the bus information and
device information is needed. Only the specific bus knows the meaning of
an device's id, so I think the bus type should provide a callback to
interpret device id.

Thanks,
Shaohua


  reply	other threads:[~2004-10-21  1:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-19  9:11 Li, Shaohua
2004-10-20  3:51 ` [ACPI] " Dmitry Torokhov
2004-10-20 17:02   ` David Brownell
2004-10-21  1:33     ` Li Shaohua [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-10-19  3:41 David Brownell
2004-10-19  4:55 ` [ACPI] " Hiroshi 2 Itoh
2004-10-19  5:18   ` David Brownell

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=1098322408.6132.44.camel@sli10-desk.sh.intel.com \
    --to=shaohua.li@intel.com \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=david-b@pacbell.net \
    --cc=dtor_core@ameritech.net \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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
all inboxes | Powered by JetHome®