From: Krzysztof Kozlowski <krzk@kernel.org>
To: Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
arm@kernel.org
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
Kukjin Kim <kgene@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL 3/3] ARM: samsung: Changes for v5.2
Date: Sun, 14 Apr 2019 17:48:05 +0200 [thread overview]
Message-ID: <20190414154805.10188-3-krzk@kernel.org> (raw)
In-Reply-To: <20190414154805.10188-1-krzk@kernel.org>
The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:
Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git tags/samsung-soc-5.2
for you to fetch changes up to 7676e667c841375b41d9438b559756141aa93d0e:
ARM: s3c64xx: Tidy up handling of regulator GPIO lookups (2019-04-14 12:53:03 +0200)
----------------------------------------------------------------
Samsung mach/soc changes for v5.2
1. Cleanup in mach code.
2. Add necessary fixes for Suspend to RAM on Exynos5422 boards (tested
with Odroid XU3/XU4/HC1 family). Finally this brings a working S2R
on these Odroid boards (still other drivers might have some issues
but mach code seems to be finished).
3. Require MCPM for Exynos542x boards because otherwise not all of cores
will come online.
4. GPIO regulator cleanup on S3C6410 Craig.
----------------------------------------------------------------
Charles Keepax (1):
ARM: s3c64xx: Tidy up handling of regulator GPIO lookups
Joonyoung Shim (1):
ARM: exynos: Add CPU state management for Exynos542x under secure firmware
Marek Szyprowski (5):
ARM: exynos: Move Exynos542x CPU state reset to pm_prepare()
ARM: exynos: Add Exynos SMC values for secure memory write
ARM: exynos: Fix undefined instruction during Exynos5422 resume
ARM: exynos: Fix infinite loops on CPU powerup failure
ARM: exynos: Set MCPM as mandatory for Exynos542x/5800 SoCs
Wen Yang (1):
ARM: exynos: Fix a leaked reference by adding missing of_node_put
arch/arm/configs/exynos_defconfig | 1 -
arch/arm/configs/multi_v7_defconfig | 1 -
arch/arm/mach-exynos/Kconfig | 12 ++-----
arch/arm/mach-exynos/Makefile | 2 +-
arch/arm/mach-exynos/common.h | 1 +
arch/arm/mach-exynos/exynos.c | 3 ++
arch/arm/mach-exynos/firmware.c | 1 +
arch/arm/mach-exynos/mcpm-exynos.c | 13 +++++++-
arch/arm/mach-exynos/platsmp.c | 9 ++++-
arch/arm/mach-exynos/smc.h | 7 ++++
arch/arm/mach-exynos/suspend.c | 49 ++++++++++++++++++++++++----
arch/arm/mach-s3c64xx/mach-crag6410-module.c | 14 ++++++--
12 files changed, 89 insertions(+), 24 deletions(-)
next prev parent reply other threads:[~2019-04-14 15:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-14 15:48 [GIT PULL 1/3] ARM: dts: exynos: Changes for v5.2 Krzysztof Kozlowski
2019-04-14 15:48 ` [GIT PULL 2/3] arm64: " Krzysztof Kozlowski
2019-04-28 19:30 ` Olof Johansson
2019-04-14 15:48 ` Krzysztof Kozlowski [this message]
2019-04-29 6:05 ` [GIT PULL 3/3] ARM: samsung: " Olof Johansson
2019-04-29 6:53 ` Krzysztof Kozlowski
2019-04-29 7:11 ` Olof Johansson
2019-04-28 19:29 ` [GIT PULL 1/3] ARM: dts: exynos: " Olof Johansson
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=20190414154805.10188-3-krzk@kernel.org \
--to=krzk@kernel.org \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=kgene@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=olof@lixom.net \
/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