From: Abhijeet Dharmapurikar <adharmap@codeaurora.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
Jean Delvare <khali@linux-fr.org>, Rajendra Nayak <rnayak@ti.com>,
Kevin Hilman <khilman@deeprootsystems.com>,
Vishwanath BS <vishwanath.bs@ti.com>,
Partha Basak <p-basak2@ti.com>,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: i2c runtime suspend and system wide suspend
Date: Wed, 29 Dec 2010 20:39:26 -0800 [thread overview]
Message-ID: <4D1C0CFE.5010008@codeaurora.org> (raw)
The i2c-core driver mixes runtime suspend and system wide suspend, in
that, during a system wide suspend, it skips calling ->suspend if the
device is runtime suspended.
I have an interrupt controller running over the i2c bus and that driver
is oblivious of the runtime pm framework, IOW, it doesn't do any runtime
pm calls. CONFIG_RUNTIME_PM is enabled however (for some other bus
drivers). The issue I am facing is that all such i2c devices are assumed
runtime suspended and the ->suspend for these devices is not invoked
during systemwide suspend.
Looking around in pci and platform busses, they don't skip calling the
->suspend callback, actually, they dont check if the device is runtime
suspended.
The question is, why do we have this special check in i2c bus driver?
Pasted below is the relevant commit.
commit 2f60ba706bd9af84c4eab704243b262e69556f2e
i2c: Fix bus-level power management callbacks
There are three issues with the i2c bus type's power management
callbacks at the moment. ....
....
....
.... Finally, the system sleep PM
(ie. suspend/resume) callbacks don't check if the device has been
already suspended at run time, in which case they should skip
suspending it. Also, it looks like the i2c bus type can use the
generic subsystem-level runtime PM callbacks.
For these reasons, rework the system sleep PM callbacks provided by
the i2c bus type to handle hibernation correctly and to invoke the
"legacy" callbacks for drivers that provide them. In addition to
that make the i2c bus type use the generic subsystem-level runtime
PM callbacks.
Thanks,
Abhijeet
--
Sent by an employee of Qualcomm Innovation Center, Inc. The Qualcomm
Innovation Center, Inc. is a member of Code Aurora Forum.
next reply other threads:[~2010-12-30 4:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-30 4:39 Abhijeet Dharmapurikar [this message]
2010-12-30 6:32 ` i2c runtime suspend and system wide suspend Rabin Vincent
2010-12-30 10:49 ` Rafael J. Wysocki
2010-12-30 10:49 ` Rafael J. Wysocki
2010-12-30 11:35 ` Mark Brown
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=4D1C0CFE.5010008@codeaurora.org \
--to=adharmap@codeaurora.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=khali@linux-fr.org \
--cc=khilman@deeprootsystems.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=p-basak2@ti.com \
--cc=rjw@sisk.pl \
--cc=rnayak@ti.com \
--cc=vishwanath.bs@ti.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).