From: Sekhar Nori <nsekhar@ti.com> To: Tony Lindgren <tony@atomide.com>, Russell King <rmk+kernel@arm.linux.org.uk> Cc: Sekhar Nori <nsekhar@ti.com>, Linux OMAP Mailing List <linux-omap@vger.kernel.org>, Santosh Shilimkar <santosh.shilimkar@ti.com>, Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org> Subject: [PATCH v3 0/3] ARM: OMAP2+: AM437x: L2 cache support Date: Tue, 22 Apr 2014 13:58:00 +0530 [thread overview] Message-ID: <cover.1398149526.git.nsekhar@ti.com> (raw) This patch series adds L2 cache support for AM437x and does some clean-ups for existing OMAP4 support along the way (no functional changes). On OMAP4 Panda, the Aux control value remains 0x7e470000 before and after the series. Tested on OMAP4 Panda and AM437x EPOS EVMs. It is based on RMK's 75 patch series titled "l2c series" + the patch contained in https://www.mail-archive.com/linux-omap@vger.kernel.org/msg103439.html Sekhar Nori (3): ARM: OMAP2+: L2 cache: get rid of init call ARM: OMAP2+: L2 cache: git rid of redundant cache replacement policy setting ARM: OMAP2+: AM43x: L2 cache support arch/arm/mach-omap2/Kconfig | 1 + arch/arm/mach-omap2/common.h | 1 + arch/arm/mach-omap2/io.c | 2 ++ arch/arm/mach-omap2/omap4-common.c | 17 ++++------------- 4 files changed, 8 insertions(+), 13 deletions(-) -- 1.7.10.1
WARNING: multiple messages have this Message-ID (diff)
From: nsekhar@ti.com (Sekhar Nori) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH v3 0/3] ARM: OMAP2+: AM437x: L2 cache support Date: Tue, 22 Apr 2014 13:58:00 +0530 [thread overview] Message-ID: <cover.1398149526.git.nsekhar@ti.com> (raw) This patch series adds L2 cache support for AM437x and does some clean-ups for existing OMAP4 support along the way (no functional changes). On OMAP4 Panda, the Aux control value remains 0x7e470000 before and after the series. Tested on OMAP4 Panda and AM437x EPOS EVMs. It is based on RMK's 75 patch series titled "l2c series" + the patch contained in https://www.mail-archive.com/linux-omap at vger.kernel.org/msg103439.html Sekhar Nori (3): ARM: OMAP2+: L2 cache: get rid of init call ARM: OMAP2+: L2 cache: git rid of redundant cache replacement policy setting ARM: OMAP2+: AM43x: L2 cache support arch/arm/mach-omap2/Kconfig | 1 + arch/arm/mach-omap2/common.h | 1 + arch/arm/mach-omap2/io.c | 2 ++ arch/arm/mach-omap2/omap4-common.c | 17 ++++------------- 4 files changed, 8 insertions(+), 13 deletions(-) -- 1.7.10.1
next reply other threads:[~2014-04-22 8:28 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-04-22 8:28 Sekhar Nori [this message] 2014-04-22 8:28 ` [PATCH v3 0/3] ARM: OMAP2+: AM437x: L2 cache support Sekhar Nori 2014-04-22 8:28 ` [PATCH v3 1/3] ARM: OMAP2+: L2 cache: get rid of init call Sekhar Nori 2014-04-22 8:28 ` Sekhar Nori 2014-04-22 8:28 ` [PATCH v3 2/3] ARM: OMAP2+: L2 cache: git rid of redundant cache replacement policy setting Sekhar Nori 2014-04-22 8:28 ` Sekhar Nori 2014-04-22 8:28 ` [PATCH v3 3/3] ARM: OMAP2+: AM43x: L2 cache support Sekhar Nori 2014-04-22 8:28 ` Sekhar Nori 2014-04-22 18:20 ` [PATCH v3 0/3] ARM: OMAP2+: AM437x: " Santosh Shilimkar 2014-04-22 18:20 ` Santosh Shilimkar 2014-04-23 18:11 ` Russell King - ARM Linux 2014-04-23 18:11 ` Russell King - ARM Linux
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.1398149526.git.nsekhar@ti.com \ --to=nsekhar@ti.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-omap@vger.kernel.org \ --cc=rmk+kernel@arm.linux.org.uk \ --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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.