From: Dmitry Torokhov <dtor_core@ameritech.net>
To: acpi-devel@lists.sourceforge.net
Cc: "Li, Shaohua" <shaohua.li@intel.com>,
David Brownell <david-b@pacbell.net>,
"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: Tue, 19 Oct 2004 22:51:13 -0500 [thread overview]
Message-ID: <200410192251.14740.dtor_core@ameritech.net> (raw)
In-Reply-To: <16A54BF5D6E14E4D916CE26C9AD3057559A042@pdsmsx402.ccr.corp.intel.com>
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.
> 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.
--
Dmitry
WARNING: multiple messages have this Message-ID (diff)
From: Dmitry Torokhov <dtor_core@ameritech.net>
To: acpi-devel@lists.sourceforge.net
Cc: "Li, Shaohua" <shaohua.li@intel.com>,
"David Brownell" <david-b@pacbell.net>,
"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: Tue, 19 Oct 2004 22:51:13 -0500 [thread overview]
Message-ID: <200410192251.14740.dtor_core@ameritech.net> (raw)
In-Reply-To: <16A54BF5D6E14E4D916CE26C9AD3057559A042@pdsmsx402.ccr.corp.intel.com>
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.
> 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.
--
Dmitry
next prev parent reply other threads:[~2004-10-20 3:51 UTC|newest]
Thread overview: 10+ 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-19 9:11 ` Li, Shaohua
2004-10-20 3:51 ` Dmitry Torokhov [this message]
2004-10-20 3:51 ` [ACPI] " Dmitry Torokhov
2004-10-20 17:02 ` David Brownell
2004-10-20 17:02 ` David Brownell
[not found] ` <200410201002.58172.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2004-10-21 1:33 ` Li Shaohua
2004-10-21 1:33 ` [ACPI] " Li Shaohua
-- 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=200410192251.14740.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=acpi-devel@lists.sourceforge.net \
--cc=david-b@pacbell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.