From: Tony Lindgren <tony@atomide.com>
To: arm@kernel.org
Cc: Tony Lindgren <tony@atomide.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 3/6] am335x and am437x pm for v4.17
Date: Mon, 5 Mar 2018 10:11:03 -0800 [thread overview]
Message-ID: <pull-1520273005-304551@atomide.com-3> (raw)
In-Reply-To: <pull-1520273005-304551@atomide.com>
In-Reply-To: <pull-1520273005-304551@atomide.com>
From: "Tony Lindgren" <tony@atomide.com>
The following changes since commit 7928b2cbe55b2a410a0f5c1f154610059c57b1b2:
Linux 4.16-rc1 (2018-02-11 15:04:29 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v4.17/am-pm-signed
for you to fetch changes up to afe761f8d3e99155b76833421e76553a3ac69577:
soc: ti: Add pm33xx driver for basic suspend support (2018-02-27 08:53:46 -0800)
----------------------------------------------------------------
Add am335x and am437x PM code for v4.17
This series of changes from Dave Gerlach adds the PM related
code to allow low-power suspend states. The code consists of
the SoC specific assembly code and a related PM driver.
----------------------------------------------------------------
Dave Gerlach (4):
ARM: OMAP2+: Introduce low-level suspend code for AM33XX
ARM: OMAP2+: Introduce low-level suspend code for AM43XX
ARM: OMAP2+: pm33xx-core: Add platform code needed for PM
soc: ti: Add pm33xx driver for basic suspend support
Documentation/devicetree/bindings/arm/omap/mpu.txt | 16 +
arch/arm/mach-omap2/Kconfig | 1 +
arch/arm/mach-omap2/Makefile | 16 +
arch/arm/mach-omap2/common.h | 7 +
arch/arm/mach-omap2/io.c | 2 +
arch/arm/mach-omap2/pm-asm-offsets.c | 31 ++
arch/arm/mach-omap2/pm.h | 3 +
arch/arm/mach-omap2/pm33xx-core.c | 189 ++++++++++
arch/arm/mach-omap2/sleep33xx.S | 214 ++++++++++++
arch/arm/mach-omap2/sleep43xx.S | 387 +++++++++++++++++++++
drivers/soc/ti/Kconfig | 9 +
drivers/soc/ti/Makefile | 1 +
drivers/soc/ti/pm33xx.c | 349 +++++++++++++++++++
include/linux/platform_data/pm33xx.h | 42 +++
14 files changed, 1267 insertions(+)
create mode 100644 arch/arm/mach-omap2/pm-asm-offsets.c
create mode 100644 arch/arm/mach-omap2/pm33xx-core.c
create mode 100644 arch/arm/mach-omap2/sleep33xx.S
create mode 100644 arch/arm/mach-omap2/sleep43xx.S
create mode 100644 drivers/soc/ti/pm33xx.c
create mode 100644 include/linux/platform_data/pm33xx.h
next prev parent reply other threads:[~2018-03-05 18:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 18:11 [GIT PULL 1/6] omap soc changes for v4.17 Tony Lindgren
2018-03-05 18:11 ` [GIT PULL 2/6] omap timer " Tony Lindgren
2018-03-07 15:21 ` Arnd Bergmann
2018-03-07 15:28 ` Tony Lindgren
2018-03-07 16:21 ` Daniel Lezcano
2018-03-05 18:11 ` Tony Lindgren [this message]
2018-03-07 15:26 ` [GIT PULL 3/6] am335x and am437x pm " Arnd Bergmann
2018-03-05 18:11 ` [GIT PULL 4/6] ti-sysc changes " Tony Lindgren
2018-03-07 15:27 ` Arnd Bergmann
2018-03-05 18:11 ` [GIT PULL 5/6] omap dts " Tony Lindgren
2018-03-07 14:39 ` Arnd Bergmann
2018-03-05 18:11 ` [GIT PULL 6/6] dra7 sdhci " Tony Lindgren
2018-03-07 14:40 ` Arnd Bergmann
2018-03-07 15:04 ` Tony Lindgren
2018-03-07 15:07 ` Arnd Bergmann
2018-03-07 15:15 ` [GIT PULL 1/6] omap soc " Arnd Bergmann
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=pull-1520273005-304551@atomide.com-3 \
--to=tony@atomide.com \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.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