From: d-gerlach@ti.com (Dave Gerlach)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 5/6] ARM: OMAP2+: Remove legacy sram init code for omap3 platforms
Date: Mon, 9 May 2016 16:49:25 -0500 [thread overview]
Message-ID: <1462830566-28708-6-git-send-email-d-gerlach@ti.com> (raw)
In-Reply-To: <1462830566-28708-1-git-send-email-d-gerlach@ti.com>
Remove omap3 platforms from using legacy sram init code in mach-omap2 as
the platforms will now use the generic mmio-sram driver like other omap
platforms already do.
Signed-off-by: Dave Gerlach <d-gerlach@ti.com>
---
arch/arm/mach-omap2/pdata-quirks.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/arch/arm/mach-omap2/pdata-quirks.c b/arch/arm/mach-omap2/pdata-quirks.c
index a935d28443da..1a5b8afdb2e3 100644
--- a/arch/arm/mach-omap2/pdata-quirks.c
+++ b/arch/arm/mach-omap2/pdata-quirks.c
@@ -579,8 +579,7 @@ void __init pdata_quirks_init(const struct of_device_id *omap_dt_match_table)
* We still need this for omap2420 and omap3 PM to work, others are
* using drivers/misc/sram.c already.
*/
- if (of_machine_is_compatible("ti,omap2420") ||
- of_machine_is_compatible("ti,omap3"))
+ if (of_machine_is_compatible("ti,omap2420"))
omap_sdrc_init(NULL, NULL);
pdata_quirks_check(auxdata_quirks);
--
2.7.3
next prev parent 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 [PATCH 0/6] ARM: OMAP3: Convert OMAP3 PM code to use generic sram driver Dave Gerlach
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 ` Dave Gerlach [this message]
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-6-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).