From: David Brownell <david-b@pacbell.net>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: acpi-devel@lists.sourceforge.net, "Li,
Shaohua" <shaohua.li@intel.com>,
"Brown, Len" <len.brown@intel.com>, Pavel Machek <pavel@ucw.cz>,
linux-kernel@vger.kernel.org
Subject: Re: [ACPI] RE: PATCH/RFC: driver model/pmcore wakeup hooks (1/4)
Date: Wed, 20 Oct 2004 10:02:57 -0700 [thread overview]
Message-ID: <200410201002.58172.david-b@pacbell.net> (raw)
In-Reply-To: <200410192251.14740.dtor_core@ameritech.net>
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.
> > You are right, we currently haven't a method to reach the goal. To match
> > a physical device and ACPI device, we need to know the ACPI device's
> > _ADR and bus.
> > I have a toy to link the PCI device and ACPI device, and some PCI
> > function can use _SxD method and _PSx method to get some information for
> > suspend/resume.
> >
>
> The only caveat is that PCI core should not depend on ACPI because it is not
> available on all platforms, not all world is x86.
RIght! Maybe something like:
int pci_enable_wake(pci_dev, on_or_off) {
...
if (dev->platform_data)
platform_enable_wake(dev, on_or_off)
...
}
That'd call an acpi_enable_wake(). I guess OpenBoot would
do its thing, and embedded boards could do all kinds of stuff.
- Dave
next prev parent reply other threads:[~2004-10-20 17:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-19 9:11 PATCH/RFC: driver model/pmcore wakeup hooks (1/4) Li, Shaohua
2004-10-20 3:51 ` [ACPI] " Dmitry Torokhov
2004-10-20 17:02 ` David Brownell [this message]
[not found] ` <200410201002.58172.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2004-10-21 1:33 ` Li Shaohua
-- strict thread matches above, loose matches on Subject: below --
2004-10-19 4:55 Hiroshi 2 Itoh
2004-10-19 5:18 ` [ACPI] " 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=200410201002.58172.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=acpi-devel@lists.sourceforge.net \
--cc=dtor_core@ameritech.net \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--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