From: Anand Moon <linux.amoon@gmail.com>
To: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Rob Herring <robh+dt@kernel.org>, Kukjin Kim <kgene@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Tomasz Figa <tomasz.figa@gmail.com>,
Chanwoo Choi <cw00.choi@samsung.com>,
Pankaj Dubey <pankaj.dubey@samsung.com>
Subject: [RFC 0/2] Add support for Suspend and Resume for Exynos4412 on
Date: Wed, 13 Feb 2019 21:40:50 +0000 [thread overview]
Message-ID: <20190213214052.2427-1-linux.amoon@gmail.com> (raw)
Add support to set the Odroid U3+ device into DEEP sleep mode
and is able to resume from suspend state.
Changes base on Krxk/next/dt and worked on 5.0.0-rc6+
TODO: fix the eMMC failuer.
Any input are welcome.
Best Regards
-Anand
Anand Moon (2):
ARM: dts: exynos: Add proper regulator states for suspend-to-mem for
odroid-u3
soc: samsung: pmu: Add the PMU data of exynos4412 to support low-power
state
.../boot/dts/exynos4412-odroid-common.dtsi | 63 ++++++++++++++
arch/arm/boot/dts/exynos4412-odroidu3.dts | 3 +
drivers/soc/samsung/exynos4-pmu.c | 83 +++++++++++++++++++
include/linux/soc/samsung/exynos-regs-pmu.h | 21 +++++
4 files changed, 170 insertions(+)
--
2.20.1
next reply other threads:[~2019-02-13 21:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 21:40 Anand Moon [this message]
2019-02-13 21:40 ` [RFC 1/2] ARM: dts: exynos: Add proper regulator states for suspend-to-mem for odroid-u3 Anand Moon
2019-02-14 12:41 ` Krzysztof Kozlowski
2019-02-14 18:34 ` Anand Moon
2019-02-15 7:30 ` Krzysztof Kozlowski
2019-02-15 8:43 ` Anand Moon
2019-02-15 13:58 ` Anand Moon
2019-02-13 21:40 ` [RFC 2/2] soc: samsung: pmu: Add the PMU data of exynos4412 to support low-power state Anand Moon
2019-02-14 12:59 ` Krzysztof Kozlowski
2019-02-14 18:37 ` Anand Moon
2019-02-15 7:33 ` Krzysztof Kozlowski
2019-02-15 8:43 ` Anand Moon
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=20190213214052.2427-1-linux.amoon@gmail.com \
--to=linux.amoon@gmail.com \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=kgene@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=pankaj.dubey@samsung.com \
--cc=robh+dt@kernel.org \
--cc=tomasz.figa@gmail.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 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).