From: Dave Gerlach <d-gerlach@ti.com>
To: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Cc: Benoit Cousson <bcousson@baylibre.com>,
Tony Lindgren <tony@atomide.com>, Sekhar Nori <nsekhar@ti.com>,
Santosh Shilimkar <santosh.shilimkar@ti.com>
Subject: [PATCH v3 0/3] OMAP4+: Get rid of internal SRAM handling
Date: Wed, 10 Sep 2014 11:04:01 -0500 [thread overview]
Message-ID: <cover.1410362895.git.d-gerlach@ti.com> (raw)
v3:
Fix minor issue in last patch to check for null sram_pool if no sram
phandle is given in DT.
Make all OMAP DT only platforms (am33xx, am43xx, omap4 and omap5)
use drivers/misc/sram.c driver instead of the omap internal
implementation for SRAM handling.
Previous discussion can be found at [1].
Regards,
Dave
[1] http://lists.infradead.org/pipermail/linux-arm-kernel/2013-August/195588.html
Rajendra Nayak (3):
ARM: AM335x: Get rid of unused sram init function
ARM: OMAP4+: Move SRAM data to DT
ARM: OMAP4+: Remove static iotable mappings for SRAM
Documentation/devicetree/bindings/arm/omap/mpu.txt | 3 ++
arch/arm/boot/dts/am33xx.dtsi | 5 ++-
arch/arm/boot/dts/am4372.dtsi | 5 +++
arch/arm/boot/dts/omap4.dtsi | 6 ++++
arch/arm/boot/dts/omap5.dtsi | 8 ++++-
arch/arm/configs/omap2plus_defconfig | 1 +
arch/arm/mach-omap2/io.c | 17 ----------
arch/arm/mach-omap2/omap4-common.c | 22 +++++++++++-
arch/arm/mach-omap2/sram.c | 39 +---------------------
arch/arm/mach-omap2/sram.h | 7 ----
10 files changed, 46 insertions(+), 67 deletions(-)
--
1.9.0
next reply other threads:[~2014-09-10 16:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 16:04 Dave Gerlach [this message]
2014-09-10 16:04 ` [PATCH v3 1/3] ARM: AM335x: Get rid of unused sram init function Dave Gerlach
2014-09-10 16:04 ` [PATCH v3 2/3] ARM: OMAP4+: Move SRAM data to DT Dave Gerlach
2014-09-10 16:04 ` [PATCH v3 3/3] ARM: OMAP4+: Remove static iotable mappings for SRAM Dave Gerlach
2014-09-10 16:56 ` [PATCH v3 0/3] OMAP4+: Get rid of internal SRAM handling Nishanth Menon
2014-09-12 18:47 ` Dave Gerlach
2014-09-18 16:48 ` Tony Lindgren
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=cover.1410362895.git.d-gerlach@ti.com \
--to=d-gerlach@ti.com \
--cc=bcousson@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=santosh.shilimkar@ti.com \
--cc=tony@atomide.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).