From: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
To: Chanwoo Choi <cw00.choi@samsung.com>
Cc: Kukjin Kim <kgene@kernel.org>,
Doug Anderson <dianders@chromium.org>,
Olof Johansson <olof@lixom.net>,
Krzysztof Kozlowski <k.kozlowski@samsung.com>,
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: Mon, 30 Mar 2015 17:56:48 +0200 [thread overview]
Message-ID: <55197240.6010405@collabora.co.uk> (raw)
In-Reply-To: <5518AF17.2060207@samsung.com>
Hello Chanwoo,
Thanks a lot for your feedback.
On 03/30/2015 04:04 AM, Chanwoo Choi wrote:
>
> I faced on the similiar issue. If some clock was disabled,
> Exynos SoC could not enter the suspend mode
>
> But, I think it is not prpper method to resolve this issue.
> about that that specific clock (e.g., mdma0) is handled in this dirver.
> Also, ARM-64bit don't include any '../mach-exynos' directory.
>
> IMHO, some clock issue have to be handled in SoC clk driver or others.
>
Ok, Abhilash also said that before so I just posted another RFC:
"[RFC PATCH v3 0/2] ARM: EXYNOS: Fix Suspend-to-RAM on Exynos5420"
Please let me know if that is more aligned to what you were
thinking as the proper solution.
>
> Best Regards,
> Chanwoo Choi
>
Best regards,
Javier
prev parent reply other threads:[~2015-03-30 15:57 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
2015-03-30 2:04 ` Chanwoo Choi
2015-03-30 15:56 ` Javier Martinez Canillas [this message]
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=55197240.6010405@collabora.co.uk \
--to=javier.martinez@collabora.co.uk \
--cc=amit.kucheria@linaro.org \
--cc=cw00.choi@samsung.com \
--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