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 00:34:18 +0100 [thread overview]
Message-ID: <20100804233418.GA8167@srcf.ucam.org> (raw)
In-Reply-To: <BLU102-W14E1E8D6FA2F2A23C56E84EBAF0@phx.gbl>
On Thu, Aug 05, 2010 at 04:13:42AM +0530, Raj Kumar wrote:
> I have implemented run time power management in my drivers. Do you mean to
> say
> In case of ACPI also, again run time power management will get to device
> in low
> power mode or full working mode.
Unless you're coding for an ACPIPNP device, you don't need to care about
ACPI at all in your driver. The code in 2.6.35 and higher will handle
that for you.
> The another thing is suppose BIOS is ACPI based, ok as you told that bus
> will handle
> all the things do you mean ACPI driver will notify the bus about various
> device states?
The core ACPI code will inform the PCI code (for instance) that a wakeup
event has been generated, or the PCI code (for instance) will call the
appropraite ACPI functions while putting the device in a low power
state.
> If yes then what the standard interface between bus driver and device
> driver?
It's documented in the runtime pm document I pointed you at.
> Do you mean if there is ACPI, still ACPI is hooked with standard linux
> static power management
> core and run time power management core?
Yes.
> I mean to say ACPI notify the bus via linux power management core (static
> and run time)?
Yes.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2010-08-04 23:34 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 [this message]
2010-08-05 10:51 ` Raj Kumar
2010-08-05 11:55 ` Matthew Garrett
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=20100804233418.GA8167@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).