From: Florian Fainelli <florian@openwrt.org>
To: <linux-mips@linux-mips.org>
Cc: <ralf@linux-mips.org>, <blogic@openwrt.org>, <jogo@openwrt.org>,
<mbizon@freebox.fr>, <cernekee@gmail.com>, <dgcbueu@gmail.com>,
Florian Fainelli <florian@openwrt.org>
Subject: [PATCH 3/3] MIPS: BCM63XX: select correct MIPS_L1_CACHE_SHIFT value
Date: Fri, 10 Jan 2014 12:35:14 -0800 [thread overview]
Message-ID: <1389386114-31834-4-git-send-email-florian@openwrt.org> (raw)
In-Reply-To: <1389386114-31834-1-git-send-email-florian@openwrt.org>
Broadcom BCM63xx DSL SoCs have a L1-cache line size of 16 bytes (shift
value of 4) instead of the currently configured 32 bytes L1-cache line
size.
Reported-by: Daniel Gonzalez <dgcbueu@gmail.com>
Signed-off-by: Florian Fainelli <florian@openwrt.org>
---
arch/mips/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/mips/Kconfig b/arch/mips/Kconfig
index 123f7c0..a3fec87 100644
--- a/arch/mips/Kconfig
+++ b/arch/mips/Kconfig
@@ -139,6 +139,7 @@ config BCM63XX
select SWAP_IO_SPACE
select ARCH_REQUIRE_GPIOLIB
select HAVE_CLK
+ select MIPS_L1_CACHE_SHIFT_4
help
Support for BCM63XX based boards
--
1.8.3.2
WARNING: multiple messages have this Message-ID (diff)
From: Florian Fainelli <florian@openwrt.org>
To: linux-mips@linux-mips.org
Cc: ralf@linux-mips.org, blogic@openwrt.org, jogo@openwrt.org,
mbizon@freebox.fr, cernekee@gmail.com, dgcbueu@gmail.com,
Florian Fainelli <florian@openwrt.org>
Subject: [PATCH 3/3] MIPS: BCM63XX: select correct MIPS_L1_CACHE_SHIFT value
Date: Fri, 10 Jan 2014 12:35:14 -0800 [thread overview]
Message-ID: <1389386114-31834-4-git-send-email-florian@openwrt.org> (raw)
Message-ID: <20140110203514.f5c-_sZ-rNJxpU7I7KuUpsAa2q5fhcArPnx-Xi0davc@z> (raw)
In-Reply-To: <1389386114-31834-1-git-send-email-florian@openwrt.org>
Broadcom BCM63xx DSL SoCs have a L1-cache line size of 16 bytes (shift
value of 4) instead of the currently configured 32 bytes L1-cache line
size.
Reported-by: Daniel Gonzalez <dgcbueu@gmail.com>
Signed-off-by: Florian Fainelli <florian@openwrt.org>
---
arch/mips/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/mips/Kconfig b/arch/mips/Kconfig
index 123f7c0..a3fec87 100644
--- a/arch/mips/Kconfig
+++ b/arch/mips/Kconfig
@@ -139,6 +139,7 @@ config BCM63XX
select SWAP_IO_SPACE
select ARCH_REQUIRE_GPIOLIB
select HAVE_CLK
+ select MIPS_L1_CACHE_SHIFT_4
help
Support for BCM63XX based boards
--
1.8.3.2
next prev parent reply other threads:[~2014-01-10 20:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 20:35 [PATCH 0/3] MIPS: L1_CACHE_SHIFT updates Florian Fainelli
2014-01-10 20:35 ` Florian Fainelli
2014-01-10 20:35 ` [PATCH 1/3] MIPS: introduce MIPS_L1_CACHE_SHIFT_<N> Florian Fainelli
2014-01-10 20:35 ` Florian Fainelli
2014-01-11 10:44 ` Jonas Gorski
2014-01-10 20:35 ` [PATCH 2/3] MIPS: update MIPS_L1_CACHE_SHIFT based on MIPS_L1_CACHE_SHIFT_<N> Florian Fainelli
2014-01-10 20:35 ` Florian Fainelli
2014-01-11 10:47 ` Jonas Gorski
2014-01-10 20:35 ` Florian Fainelli [this message]
2014-01-10 20:35 ` [PATCH 3/3] MIPS: BCM63XX: select correct MIPS_L1_CACHE_SHIFT value Florian Fainelli
2014-01-11 10:45 ` John Crispin
2014-01-11 10:54 ` Jonas Gorski
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=1389386114-31834-4-git-send-email-florian@openwrt.org \
--to=florian@openwrt.org \
--cc=blogic@openwrt.org \
--cc=cernekee@gmail.com \
--cc=dgcbueu@gmail.com \
--cc=jogo@openwrt.org \
--cc=linux-mips@linux-mips.org \
--cc=mbizon@freebox.fr \
--cc=ralf@linux-mips.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 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.