From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Raj Kumar <rajkumar278@hotmail.com>
Cc: linux-acpi@vger.kernel.org
Subject: Re: Question regarding linux acpi
Date: Thu, 5 Aug 2010 12:55:25 +0100 [thread overview]
Message-ID: <20100805115525.GA18337@srcf.ucam.org> (raw)
In-Reply-To: <BLU102-W143744C8470E5E9C2F4B8EEB900@phx.gbl>
On Thu, Aug 05, 2010 at 04:21:36PM +0530, Raj Kumar wrote:
> {RAJ}: Does it mean then PCI bus driver code and ACPI driver will directly communicate
> with each other without any linux power management core?
Yes, but the bus driver will then call the power management core.
> {RAJ}: If system suspend/resumes and runtime_suspend/runtime_resume happens, as linux power management core(static/runtime)
> calls the bus driver code so when ACPI will be there, the bus driver will directly call the ACPI driver APIs.
When ACPI is available, yes.
> But still device driver's suspend and resume(static and runtime) calls will be called by bus driver as normal behaviour
> and if ACPI is there, then bus driver will inform the device driver and then inform the device power status to ACPI driver?
The device driver may call back into the bus driver, and that may in
turn trigger an ACPI call. PCI is the best example of this - check out
the pci_platform_pm_ops structure in pci-acpi.c for example.
> {RAJ}: Will the ACPI driver code also call the linux power management functions directly?
For runtime power management? No.
--
Matthew Garrett | mjg59@srcf.ucam.org
prev parent reply other threads:[~2010-08-05 11:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 15:51 Question regarding linux acpi Raj Kumar
2010-08-04 17:02 ` Matthew Garrett
[not found] ` <BLU102-W81BE50E68610AAA92C33AEBAF0@phx.gbl>
2010-08-04 20:22 ` Matthew Garrett
[not found] ` <BLU102-W14E1E8D6FA2F2A23C56E84EBAF0@phx.gbl>
2010-08-04 23:34 ` Matthew Garrett
2010-08-05 10:51 ` Raj Kumar
2010-08-05 11:55 ` Matthew Garrett [this message]
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=20100805115525.GA18337@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=linux-acpi@vger.kernel.org \
--cc=rajkumar278@hotmail.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;
as well as URLs for NNTP newsgroup(s).