From: kesavan.abhilash@gmail.com (Abhilash Kesavan)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v9 0/2] Adds PMU and S2R support for exynos5420
Date: Thu, 9 Oct 2014 08:07:39 +0530 [thread overview]
Message-ID: <CAM4voanoOV44EQveAeikp1P0bXCU8HHdX2XDi3jwLkfQOP0CNQ@mail.gmail.com> (raw)
In-Reply-To: <7hiojuno9e.fsf@deeprootsystems.com>
Hi Kevin,
On Thu, Oct 9, 2014 at 4:49 AM, Kevin Hilman <khilman@kernel.org> wrote:
> Vikas Sajjan <vikas.sajjan@samsung.com> writes:
>
> [...]
>
>> Tested on Kukjin Kim's tree, for-next branch +
>> 1] http://www.spinics.net/lists/linux-samsung-soc/msg33750.html
>> 2] https://www.mail-archive.com/linux-samsung-soc at vger.kernel.org/msg37260.html
>> 3] with the CLK_IGNORE_UNUSED flag for aclk200_disp1 CLK
>>
>> on Exynos5420 based chromebook (peach-pit board)
>>
>> Below procedures were followed to test S2R:
>> Procedure A:
>> 1. make multi_v7_defconfig
>> 2 enable MCPM for 5420
>> 3. enable S3C RTC
>> 5. echo +20 > /sys/class/rtc/rtc0/wakealarm && echo mem > /sys/power/state
>> Procedure B:
>> 1. make exynos_defconfig
>> 4. echo +20 > /sys/class/rtc/rtc0/wakealarm && echo mem > /sys/power/state
>
> I went tried to this on exynos5800-peach-pi and found first that
> exynos_defonfig is missing the MAX77802 kconfig options for the RTC
> source clock:
>
> CONFIG_REGULATOR_MAX77802=y
> CONFIG_COMMON_CLK_MAX77802=y
I am using exynos_defconfig (no changes) with the internal SoC RTC
which is enabled by default. I did not enable the MAX77802 RTC.
>
> With those, rtc0 then comes up, but isn't waking from suspend. However,
> writing something to rtc0/wakealarm does result in /proc/interrupts
> having an interrupt for the RTC, it's just not waking the system.
>
> Anyone else tried this on 5800/peach-pi?
I have tested this on a Peach-Pi and the system is resuming fine. The
patches applied on kgene's for-next branch along with the
aclk200_disp1 fix are:
http://lkml.org/lkml/2014/9/30/156
https://lkml.org/lkml/2014/10/6/89
http://www.spinics.net/lists/arm-kernel/msg368207.html
http://www.spinics.net/lists/linux-samsung-soc/msg37647.html
Abhilash
next prev parent reply other threads:[~2014-10-09 2:37 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
2014-10-08 11:55 ` Javier Martinez Canillas
2014-10-08 23:19 ` Kevin Hilman
2014-10-09 2:37 ` Abhilash Kesavan [this message]
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=CAM4voanoOV44EQveAeikp1P0bXCU8HHdX2XDi3jwLkfQOP0CNQ@mail.gmail.com \
--to=kesavan.abhilash@gmail.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).