linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/3] omap soc chages for v4.18 merge window
Date: Mon, 21 May 2018 12:41:31 -0700	[thread overview]
Message-ID: <pull-1526925630-789198@atomide.com-2> (raw)
In-Reply-To: <pull-1526925630-789198@atomide.com>

From: "Tony Lindgren" <tony@atomide.com>

The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338:

  Linux 4.17-rc1 (2018-04-15 18:24:20 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v4.18/soc-signed

for you to fetch changes up to 3bb3799cd4233b7c24622ae8c41455fb27a55c0f:

  Merge branch 'omap-for-v4.18/soc-fixes' into omap-for-v4.18/soc (2018-05-21 10:34:17 -0700)

----------------------------------------------------------------
SoC changes for omap variants for v4.18 merge window

This series mostly adds saving of power and clock domain registers for
am335x/am437x suspend to RTC only mode. There is also a non-urgent fix
for omap4 PM where we could end up losing GPIO interrupts if bootloader
has LOGICRETSTATE cleared for domains. And there is a clean-up patch for
omap1 to use device properties for at24 eeprom.

----------------------------------------------------------------
Bartosz Golaszewski (1):
      ARM: omap1: osk: use device properties for at24 eeprom

Dave Gerlach (1):
      ARM: OMAP2+: prm44xx: Introduce context save/restore for am43 PRCM IO

Keerthy (3):
      ARM: OMAP2+: clockdomain: Inroduce cpu_pm notifiers for context save/restore
      ARM: OMAP2+: powerdomain: Introduce cpu_pm notifiers for context save/restore
      ARM: OMAP2+: prm44xx: Inroduce cpu_pm notifiers for context save/restore

Russ Dill (2):
      ARM: OMAP2+: Add functions to save and restore clockdomain context en-masse.
      ARM: OMAP2+: Add functions to save and restore powerdomain context

Tony Lindgren (2):
      ARM: OMAP2+: Make sure LOGICRETSTATE bits are not cleared
      Merge branch 'omap-for-v4.18/soc-fixes' into omap-for-v4.18/soc

 arch/arm/mach-omap1/board-osk.c   |  10 ++--
 arch/arm/mach-omap2/clockdomain.c |  73 ++++++++++++++++++++++++++
 arch/arm/mach-omap2/clockdomain.h |   8 +++
 arch/arm/mach-omap2/cm33xx.c      |  53 +++++++++++++++++++
 arch/arm/mach-omap2/cminst44xx.c  |  43 ++++++++++++++++
 arch/arm/mach-omap2/pm44xx.c      |  13 +++++
 arch/arm/mach-omap2/powerdomain.c |  87 +++++++++++++++++++++++++++++++
 arch/arm/mach-omap2/powerdomain.h |   7 +++
 arch/arm/mach-omap2/prm33xx.c     |  31 ++++++++++++
 arch/arm/mach-omap2/prm44xx.c     | 104 ++++++++++++++++++++++++++++++++++++++
 10 files changed, 424 insertions(+), 5 deletions(-)

  reply	other threads:[~2018-05-21 19:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-21 19:41 [GIT PULL 1/3] ti-sysc array access fix for v4.18 merge window Tony Lindgren
2018-05-21 19:41 ` Tony Lindgren [this message]
2018-05-25 21:13   ` [GIT PULL 2/3] omap soc chages " Olof Johansson
2018-05-21 19:41 ` [GIT PULL 3/3] more omap dts changes " Tony Lindgren
2018-05-25 21:14   ` Olof Johansson
2018-05-25 21:12 ` [GIT PULL 1/3] ti-sysc array access fix " 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=pull-1526925630-789198@atomide.com-2 \
    --to=tony@atomide.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).