From: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
To: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Cc: Kukjin Kim <kgene@kernel.org>,
Doug Anderson <dianders@chromium.org>,
Olof Johansson <olof@lixom.net>,
Abhilash Kesavan <kesavan.abhilash@gmail.com>,
Kevin Hilman <khilman@linaro.org>,
Tyler Baker <tyler.baker@linaro.org>,
Steve Capper <steve.capper@linaro.org>,
Amit Kucheria <amit.kucheria@linaro.org>,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 2/2] ARM: EXYNOS: Make sure that the Exynos5420 MDMA0 clock is enabled during suspend
Date: Fri, 27 Mar 2015 16:15:23 +0100 [thread overview]
Message-ID: <5515740B.7090200@collabora.co.uk> (raw)
In-Reply-To: <CAJKOXPcak1RrvpjQNhVpd+oQODMNvbNhV0TmzO6VNsjcdqxfvw@mail.gmail.com>
Hello Krzysztof,
Thanks a lot for your feedback.
On 03/27/2015 03:38 PM, Krzysztof Kozlowski wrote:
> 2015-03-27 15:21 GMT+01:00 Javier Martinez Canillas
> <javier.martinez@collabora.co.uk>:
>> Commit ae43b3289186 ("ARM: 8202/1: dmaengine: pl330: Add runtime Power
>> Management support v12") added pm support for the pl330 dma driver but
>> it makes the clock for the Exynos5420 MDMA0 DMA controller to be gated
>> during suspend and this clock needs to remain enabled in order to make
>> the system resume from a system suspend state.
>>
>> To make sure that the clock is enabled during suspend, enable it prior
>> to entering a suspend state and disable it once the system has resumed.
>>
>> Thanks to Abhilash Kesavan for figuring out that this was the issue.
>>
>> Fixes: ae43b32 ("ARM: 8202/1: dmaengine: pl330: Add runtime Power Management support v12")
>> Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
>
> Hmmm... isn't a real problem elsewhere - like some clock hierarchy is
> wrong or incomplete? This rather looks like workaround for the
> problem.
>
That's a very good question, that's why I sent it as an RFC. I didn't find
anything relevant in the manual but I could certainly be missing something.
>>
>> @@ -516,6 +528,9 @@ static void exynos5420_pm_resume(void)
>> {
>> unsigned long tmp;
>>
>> + if (!IS_ERR_OR_NULL(clk))
>> + clk_disable_unprepare(clk);
>> +
>
> Missing clk_put()
>
Yes, Sylwester already pointed it out. Sorry for missing that.
> Best regards,
> Krzysztof
>
Best regards,
Javier
next prev parent reply other threads:[~2015-03-27 15:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 14:21 [RFC PATCH 0/2] ARM: EXYNOS: Fix Suspend-to-RAM on Exynos5420 Javier Martinez Canillas
2015-03-27 14:21 ` [RFC PATCH 1/2] clk: exynos5420: Add alias for MDMA0 controller clock Javier Martinez Canillas
2015-03-27 14:21 ` [RFC PATCH 2/2] ARM: EXYNOS: Make sure that the Exynos5420 MDMA0 clock is enabled during suspend Javier Martinez Canillas
2015-03-27 14:36 ` Sylwester Nawrocki
2015-03-27 15:11 ` Javier Martinez Canillas
2015-03-27 14:38 ` Krzysztof Kozlowski
2015-03-27 15:15 ` Javier Martinez Canillas [this message]
2015-03-30 2:04 ` Chanwoo Choi
2015-03-30 15:56 ` Javier Martinez Canillas
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=5515740B.7090200@collabora.co.uk \
--to=javier.martinez@collabora.co.uk \
--cc=amit.kucheria@linaro.org \
--cc=dianders@chromium.org \
--cc=k.kozlowski@samsung.com \
--cc=kesavan.abhilash@gmail.com \
--cc=kgene@kernel.org \
--cc=khilman@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=olof@lixom.net \
--cc=steve.capper@linaro.org \
--cc=tyler.baker@linaro.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