From: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
To: Abhilash Kesavan <kesavan.abhilash@gmail.com>
Cc: Kevin Hilman <khilman@deeprootsystems.com>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
Vikas Sajjan <vikas.sajjan@samsung.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Pankaj Dubey <pankaj.dubey@samsung.com>
Subject: Re: exynos5800-peach-pi: suspend/resume (still) broken
Date: Fri, 27 Mar 2015 14:29:35 +0100 [thread overview]
Message-ID: <55155B3F.2010704@collabora.co.uk> (raw)
In-Reply-To: <CAM4voanUg87=Ya6azGCRz8r2=WJ0wi4ktqdn6GD6ULJsnLUMmw@mail.gmail.com>
Hello Abhilash,
On 03/20/2015 06:40 PM, Abhilash Kesavan wrote:
>
> Regarding the mdma0 disablement, it looks like for the system to
> suspend properly the mdma0 pclk needs to stay on.
>
I had time today again to work on this issue and the best
place I found to enable and disable the mdma0 clock is in
exynos5420_pm_{prepare,resume}. Please let me know if you
have a better idea of where the clock should be managed.
I'll send a RFC patch-set soon.
> Regards,
> Abhilash
Best regards,
Javier
WARNING: multiple messages have this Message-ID (diff)
From: javier.martinez@collabora.co.uk (Javier Martinez Canillas)
To: linux-arm-kernel@lists.infradead.org
Subject: exynos5800-peach-pi: suspend/resume (still) broken
Date: Fri, 27 Mar 2015 14:29:35 +0100 [thread overview]
Message-ID: <55155B3F.2010704@collabora.co.uk> (raw)
In-Reply-To: <CAM4voanUg87=Ya6azGCRz8r2=WJ0wi4ktqdn6GD6ULJsnLUMmw@mail.gmail.com>
Hello Abhilash,
On 03/20/2015 06:40 PM, Abhilash Kesavan wrote:
>
> Regarding the mdma0 disablement, it looks like for the system to
> suspend properly the mdma0 pclk needs to stay on.
>
I had time today again to work on this issue and the best
place I found to enable and disable the mdma0 clock is in
exynos5420_pm_{prepare,resume}. Please let me know if you
have a better idea of where the clock should be managed.
I'll send a RFC patch-set soon.
> Regards,
> Abhilash
Best regards,
Javier
next prev parent reply other threads:[~2015-03-27 13:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 17:35 exynos5800-peach-pi: suspend/resume (still) broken Kevin Hilman
2015-03-17 17:35 ` Kevin Hilman
2015-03-18 10:31 ` Javier Martinez Canillas
2015-03-18 10:31 ` Javier Martinez Canillas
2015-03-20 14:23 ` Abhilash Kesavan
2015-03-20 14:23 ` Abhilash Kesavan
2015-03-20 16:16 ` Javier Martinez Canillas
2015-03-20 16:16 ` Javier Martinez Canillas
2015-03-20 16:29 ` Abhilash Kesavan
2015-03-20 16:29 ` Abhilash Kesavan
2015-03-20 17:40 ` Abhilash Kesavan
2015-03-20 17:40 ` Abhilash Kesavan
2015-03-20 17:52 ` Javier Martinez Canillas
2015-03-20 17:52 ` Javier Martinez Canillas
2015-03-27 13:29 ` Javier Martinez Canillas [this message]
2015-03-27 13:29 ` Javier Martinez Canillas
2015-03-27 14:06 ` Abhilash Kesavan
2015-03-27 14:06 ` Abhilash Kesavan
2015-03-27 14:30 ` Javier Martinez Canillas
2015-03-27 14:30 ` 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=55155B3F.2010704@collabora.co.uk \
--to=javier.martinez@collabora.co.uk \
--cc=kesavan.abhilash@gmail.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=pankaj.dubey@samsung.com \
--cc=vikas.sajjan@samsung.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.