From: Ulf Hansson <ulf.hansson@linaro.org>
To: Vinod Koul <vkoul@kernel.org>, dmaengine@vger.kernel.org
Cc: Marek Szyprowski <m.szyprowski@samsung.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org,
Ulf Hansson <ulf.hansson@linaro.org>
Subject: [PATCH 2/2] dmaengine: pl330: Convert to the *_late and *_early system sleep callbacks
Date: Thu, 5 Dec 2019 15:37:46 +0100 [thread overview]
Message-ID: <20191205143746.24873-3-ulf.hansson@linaro.org> (raw)
In-Reply-To: <20191205143746.24873-1-ulf.hansson@linaro.org>
It has turned out that it's in general a good idea for dmaengines to allow
DMA requests during the entire dpm_suspend() phase. Therefore, convert the
pl330 driver into using SET_LATE_SYSTEM_SLEEP_PM_OPS.
Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
---
drivers/dma/pl330.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/dma/pl330.c b/drivers/dma/pl330.c
index 8e01da157518..88b884cbb7c1 100644
--- a/drivers/dma/pl330.c
+++ b/drivers/dma/pl330.c
@@ -2981,7 +2981,9 @@ static int __maybe_unused pl330_resume(struct device *dev)
return ret;
}
-static SIMPLE_DEV_PM_OPS(pl330_pm, pl330_suspend, pl330_resume);
+static const struct dev_pm_ops pl330_pm = {
+ SET_LATE_SYSTEM_SLEEP_PM_OPS(pl330_suspend, pl330_resume)
+};
static int
pl330_probe(struct amba_device *adev, const struct amba_id *id)
--
2.17.1
next prev parent reply other threads:[~2019-12-05 14:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 14:37 [PATCH 0/2] dmaengine: pl330: A few system suspend/resume changes Ulf Hansson
2019-12-05 14:37 ` [PATCH 1/2] dmaengine: pl330: Drop boilerplate code for suspend/resume Ulf Hansson
2019-12-06 11:46 ` Marek Szyprowski
2019-12-05 14:37 ` Ulf Hansson [this message]
2019-12-06 11:46 ` [PATCH 2/2] dmaengine: pl330: Convert to the *_late and *_early system sleep callbacks Marek Szyprowski
2019-12-10 6:09 ` [PATCH 0/2] dmaengine: pl330: A few system suspend/resume changes Vinod Koul
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=20191205143746.24873-3-ulf.hansson@linaro.org \
--to=ulf.hansson@linaro.org \
--cc=dmaengine@vger.kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=vkoul@kernel.org \
/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).