From: Sameer Pujar <spujar@nvidia.com>
To: <treding@nvidia.com>, <jonathanh@nvidia.com>
Cc: <linux-tegra@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Sameer Pujar <spujar@nvidia.com>
Subject: [PATCH v2 2/2] bus: tegra-aconnect: add system sleep callbacks
Date: Wed, 13 Mar 2019 10:11:59 +0530 [thread overview]
Message-ID: <1552452119-6574-2-git-send-email-spujar@nvidia.com> (raw)
In-Reply-To: <1552452119-6574-1-git-send-email-spujar@nvidia.com>
pm_runtime_force_suspend() and pm_runtime_force_resume() are used as system
sleep noirq suspend and resume callbacks. If the driver is active till late
suspend, where runtime PM cannot run, force suspend is essential for the
device. This makes sure that the device is put into low power state during
system wide PM transitions to sleep states.
Signed-off-by: Sameer Pujar <spujar@nvidia.com>
---
drivers/bus/tegra-aconnect.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/bus/tegra-aconnect.c b/drivers/bus/tegra-aconnect.c
index 9349157..ac58142 100644
--- a/drivers/bus/tegra-aconnect.c
+++ b/drivers/bus/tegra-aconnect.c
@@ -94,6 +94,8 @@ static int tegra_aconnect_runtime_suspend(struct device *dev)
static const struct dev_pm_ops tegra_aconnect_pm_ops = {
SET_RUNTIME_PM_OPS(tegra_aconnect_runtime_suspend,
tegra_aconnect_runtime_resume, NULL)
+ SET_NOIRQ_SYSTEM_SLEEP_PM_OPS(pm_runtime_force_suspend,
+ pm_runtime_force_resume)
};
static const struct of_device_id tegra_aconnect_of_match[] = {
--
2.7.4
next prev parent reply other threads:[~2019-03-13 4:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-13 4:41 [PATCH v2 1/2] bus: tegra-aconnect: use devm_clk_*() helpers Sameer Pujar
2019-03-13 4:41 ` Sameer Pujar [this message]
2019-03-13 10:30 ` [PATCH v2 2/2] bus: tegra-aconnect: add system sleep callbacks Jon Hunter
2019-03-27 11:10 ` [PATCH v2 1/2] bus: tegra-aconnect: use devm_clk_*() helpers Sameer Pujar
2019-03-27 13:18 ` Jon Hunter
2019-03-28 16:32 ` Thierry Reding
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=1552452119-6574-2-git-send-email-spujar@nvidia.com \
--to=spujar@nvidia.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=treding@nvidia.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).