From: vikas.sajjan@samsung.com (Vikas Sajjan)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v9 0/2] Adds PMU and S2R support for exynos5420
Date: Wed, 8 Oct 2014 17:36:28 +0545 [thread overview]
Message-ID: <CAGm_ybj1DWituTMvG77+=8XY57skoLk+OwS_YLL0FXhrCOkohA@mail.gmail.com> (raw)
In-Reply-To: <CABxcv=k==kP_+fc58a6ji_O572Cxzj_EmxmRo3kbc48k-qBO-w@mail.gmail.com>
Hi Javier,
On Wed, Oct 8, 2014 at 3:42 PM, Javier Martinez Canillas
<javier@dowhile0.org> wrote:
> Hello Vikas,
>
> On Wed, Oct 8, 2014 at 11:26 AM, Vikas Sajjan <vikas.sajjan@samsung.com> wrote:
>>>>
>>>> Can you please pick this series.
>>>>
>>> Yes, sure I will queue this series after -rc1 release.
>>
>
> Not related to your series but did you figure out why the
> aclk200_disp1 and aclk300_disp1 clocks are left unused?
>
As mentioned earlier, I recently noticed that these clocks are
preventing system from suspending.
These clocks are used by the in-flight DRM display driver and once it
is merged the display driver will be handling the clock during boot-up
and suspend/resume.
In our internal tree (3.17-rc5 based) where we have DRM display driver
enabled, we do not see any issues and do not need to add the
CLK_IGNORE_UNUSED flag.
> I'm carrying your patch to flag those clocks as CLK_IGNORE_UNUSED to
> prevent being disabled by the CCF. And while that allows me to test,
> I'm afraid that it may not be the proper solution since it could just
> be hiding the real cause of the issue.
Till the DRM display driver gets merged, we can continue to use this
for testing purposes.
>
> Of course this should not block your series from been merged but I
> just wondered if you found the cause since it would be nice to have
> s2r properly working on exynos5420.
>
>> Thank you.
>>
>>>
>>> Thanks,
>>> Kukjin
>>>
>
> best regards,
> Javier
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2014-10-08 11:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 9:22 [PATCH v9 0/2] Adds PMU and S2R support for exynos5420 Vikas Sajjan
2014-10-07 9:22 ` [PATCH v9 1/2] ARM: exynos5: Add PMU support for 5420 Vikas Sajjan
2014-10-07 12:32 ` Javier Martinez Canillas
2014-10-08 8:22 ` Vikas Sajjan
2014-10-07 9:22 ` [PATCH v9 2/2] ARM: exynos5: Add Suspend-to-RAM " Vikas Sajjan
2014-10-07 12:34 ` Javier Martinez Canillas
2014-10-08 8:23 ` Vikas Sajjan
2014-10-08 8:25 ` [PATCH v9 0/2] Adds PMU and S2R support for exynos5420 Vikas Sajjan
2014-10-08 8:37 ` Kukjin Kim
2014-10-08 9:26 ` Vikas Sajjan
2014-10-08 9:57 ` Javier Martinez Canillas
2014-10-08 11:51 ` Vikas Sajjan [this message]
2014-10-08 11:55 ` Javier Martinez Canillas
2014-10-08 23:19 ` Kevin Hilman
2014-10-09 2:37 ` Abhilash Kesavan
2014-10-09 9:48 ` Javier Martinez Canillas
2014-10-09 21:50 ` Kevin Hilman
2014-10-09 22:10 ` Javier Martinez Canillas
2014-10-09 22:59 ` Kevin Hilman
2014-10-10 3:25 ` Abhilash Kesavan
2014-10-10 22:02 ` Kevin Hilman
2014-10-11 4:04 ` Vikas Sajjan
2014-10-10 11:09 ` 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='CAGm_ybj1DWituTMvG77+=8XY57skoLk+OwS_YLL0FXhrCOkohA@mail.gmail.com' \
--to=vikas.sajjan@samsung.com \
--cc=linux-arm-kernel@lists.infradead.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).