linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: d-gerlach@ti.com (Dave Gerlach)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/6] ARM: OMAP3: Convert OMAP3 PM code to use generic sram driver
Date: Mon, 9 May 2016 16:49:20 -0500	[thread overview]
Message-ID: <1462830566-28708-1-git-send-email-d-gerlach@ti.com> (raw)

Hi,
This series adds support for OMAP3 platforms to use the generic SRAM driver
at drivers/misc/sram.c. It depends on the patches sent here [1], which were
sent as an RFC so if that series does not get accepted we will need to find
a different method of marking SRAM region as executable so this series will
need to change slightly.

The idea of this series is to add the ocmcram nodes to the DT files before
converting the pm34xx to use the genalloc API allocate space for the
sleep34xx.S code so that we do not break PM. After we do the conversion
we can drop the legacy mach-omap2 SRAM code for OMAP3 as we no longer will
have any dependency on it.

Tested suspend and off-mode on omap3-beaglexm and omap3-n900, cpuidle works
fine as well.

Regards,
Dave

[1] http://lkml.iu.edu/hypermail/linux/kernel/1605.1/01069.html

Dave Gerlach (6):
  Documentation: sram: ti: Add TI SRAM bindings
  ARM: dts: omap3: Add ocmcram node
  ARM: dts: omap3-n900: Add secure reserved region to ocmcram node
  ARM: OMAP2+: pm34xx: Convert to use generic sram driver for idle code
  ARM: OMAP2+: Remove legacy sram init code for omap3 platforms
  ARM: OMAP2+: sram: remove legacy OMAP3 code

 Documentation/devicetree/bindings/sram/ti-sram.txt | 47 +++++++++++
 arch/arm/boot/dts/omap3-n900.dts                   |  7 ++
 arch/arm/boot/dts/omap3.dtsi                       | 11 +++
 arch/arm/mach-omap2/pdata-quirks.c                 |  3 +-
 arch/arm/mach-omap2/pm34xx.c                       | 98 ++++++++++++++++++----
 arch/arm/mach-omap2/sram.c                         | 23 -----
 6 files changed, 147 insertions(+), 42 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/sram/ti-sram.txt

-- 
2.7.3

             reply	other threads:[~2016-05-09 21:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-09 21:49 Dave Gerlach [this message]
2016-05-09 21:49 ` [PATCH 1/6] Documentation: sram: ti: Add TI SRAM bindings Dave Gerlach
2016-05-09 21:49 ` [PATCH 2/6] ARM: dts: omap3: Add ocmcram node Dave Gerlach
2016-05-09 21:49 ` [PATCH 3/6] ARM: dts: omap3-n900: Add secure reserved region to " Dave Gerlach
2016-05-09 21:49 ` [PATCH 4/6] ARM: OMAP2+: pm34xx: Convert to use generic sram driver for idle code Dave Gerlach
2016-05-09 21:49 ` [PATCH 5/6] ARM: OMAP2+: Remove legacy sram init code for omap3 platforms Dave Gerlach
2016-05-09 21:49 ` [PATCH 6/6] ARM: OMAP2+: sram: remove legacy OMAP3 code Dave Gerlach

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=1462830566-28708-1-git-send-email-d-gerlach@ti.com \
    --to=d-gerlach@ti.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).