From: "Álvaro Fernández Rojas" <noltari@gmail.com>
To: linux-mips@linux-mips.org, ralf@linux-mips.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
f.fainelli@gmail.com, jogo@openwrt.org, cernekee@gmail.com
Cc: "Álvaro Fernández Rojas" <noltari@gmail.com>
Subject: [PATCH v2 1/2] bmips: add BCM6358 support
Date: Sun, 21 Feb 2016 12:41:20 +0100 [thread overview]
Message-ID: <1456054881-26787-1-git-send-email-noltari@gmail.com> (raw)
BCM6358 has a shared TLB which conflicts with current SMP support, so it must
be disabled for now.
BCM6358 uses >= 0xfffe0000 addresses for internal registers, which need to be
remapped (by using a simplified version of BRCM63xx ioremap.h).
Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
---
v2: Use a different approach for remapping internal registers
arch/mips/bmips/setup.c | 29 +++++++++++++++++------
arch/mips/include/asm/mach-bmips/ioremap.h | 37 ++++++++++++++++++++++++++++++
2 files changed, 59 insertions(+), 7 deletions(-)
create mode 100644 arch/mips/include/asm/mach-bmips/ioremap.h
diff --git a/arch/mips/bmips/setup.c b/arch/mips/bmips/setup.c
index 3553528..f834a86 100644
--- a/arch/mips/bmips/setup.c
+++ b/arch/mips/bmips/setup.c
@@ -18,6 +18,7 @@
#include <linux/of_fdt.h>
#include <linux/of_platform.h>
#include <linux/smp.h>
+#include <linux/types.h>
#include <asm/addrspace.h>
#include <asm/bmips.h>
#include <asm/bootinfo.h>
@@ -35,9 +36,12 @@
static const unsigned long kbase = VMLINUX_LOAD_ADDRESS & 0xfff00000;
+phys_addr_t bmips_internal_registers;
+
struct bmips_quirk {
- const char *compatible;
- void (*quirk_fn)(void);
+ const char *compatible;
+ void (*quirk_fn)(void);
+ const phys_addr_t regs;
};
static void kbase_setup(void)
@@ -95,17 +99,27 @@ static void bcm6328_quirks(void)
bcm63xx_fixup_cpu1();
}
+static void bcm6358_quirks(void)
+{
+ /*
+ * BCM6358 needs special handling for its shared TLB, so
+ * disable SMP for now
+ */
+ bmips_smp_enabled = 0;
+}
+
static void bcm6368_quirks(void)
{
bcm63xx_fixup_cpu1();
}
static const struct bmips_quirk bmips_quirk_list[] = {
- { "brcm,bcm3384-viper", &bcm3384_viper_quirks },
- { "brcm,bcm33843-viper", &bcm3384_viper_quirks },
- { "brcm,bcm6328", &bcm6328_quirks },
- { "brcm,bcm6368", &bcm6368_quirks },
- { "brcm,bcm63168", &bcm6368_quirks },
+ { "brcm,bcm3384-viper", &bcm3384_viper_quirks, 0 },
+ { "brcm,bcm33843-viper", &bcm3384_viper_quirks, 0 },
+ { "brcm,bcm6328", &bcm6328_quirks, 0 },
+ { "brcm,bcm6358", &bcm6358_quirks, 0xfffe0000 },
+ { "brcm,bcm6368", &bcm6368_quirks, 0 },
+ { "brcm,bcm63168", &bcm6368_quirks, 0 },
{ },
};
@@ -162,6 +176,7 @@ void __init plat_mem_setup(void)
for (q = bmips_quirk_list; q->quirk_fn; q++) {
if (of_flat_dt_is_compatible(of_get_flat_dt_root(),
q->compatible)) {
+ bmips_internal_registers = q->regs;
q->quirk_fn();
}
}
diff --git a/arch/mips/include/asm/mach-bmips/ioremap.h b/arch/mips/include/asm/mach-bmips/ioremap.h
new file mode 100644
index 0000000..5ffca94
--- /dev/null
+++ b/arch/mips/include/asm/mach-bmips/ioremap.h
@@ -0,0 +1,37 @@
+#ifndef __ASM_MACH_BMIPS_IOREMAP_H
+#define __ASM_MACH_BMIPS_IOREMAP_H
+
+#include <linux/types.h>
+
+extern phys_addr_t bmips_internal_registers;
+
+static inline phys_addr_t fixup_bigphys_addr(phys_addr_t phys_addr,
+ phys_addr_t size)
+{
+ return phys_addr;
+}
+
+static inline int is_bmips_internal_registers(phys_addr_t offset)
+{
+ if (bmips_internal_registers != 0 && offset >= bmips_internal_registers)
+ return 1;
+ else
+ return 0;
+}
+
+static inline void __iomem *plat_ioremap(phys_addr_t offset,
+ unsigned long size,
+ unsigned long flags)
+{
+ if (is_bmips_internal_registers(offset))
+ return (void __iomem *) offset;
+
+ return NULL;
+}
+
+static inline int plat_iounmap(const volatile void __iomem *addr)
+{
+ return is_bmips_internal_registers((unsigned long) addr);
+}
+
+#endif /* __ASM_MACH_BMIPS_IOREMAP_H */
--
1.9.1
next reply other threads:[~2016-02-21 11:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-21 11:41 Álvaro Fernández Rojas [this message]
[not found] ` <1456054881-26787-1-git-send-email-noltari-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-03-03 20:09 ` [PATCH v2 1/2] bmips: add BCM6358 support Florian Fainelli
2016-04-03 9:56 ` [PATCH v3 " Álvaro Fernández Rojas
[not found] ` <1459677376-10449-1-git-send-email-noltari-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-04-03 9:56 ` [PATCH v3 2/2] bmips: add device tree example for BCM6358 Álvaro Fernández Rojas
2016-04-04 5:16 ` Rob Herring
2016-04-04 8:09 ` [PATCH v4 1/2] bmips: add BCM6358 support Álvaro Fernández Rojas
[not found] ` <1459757353-14683-1-git-send-email-noltari-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-04-04 8:09 ` [PATCH v4 2/2] bmips: add device tree example for BCM6358 Álvaro Fernández Rojas
[not found] ` <1459757353-14683-2-git-send-email-noltari-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-04-07 17:57 ` Rob Herring
2016-04-09 10:56 ` [PATCH 1/2] bmips: add BCM6358 support Álvaro Fernández Rojas
2016-04-09 10:56 ` [PATCH 2/2] bmips: add device tree example for BCM6358 Álvaro Fernández Rojas
[not found] ` <1460199408-18738-2-git-send-email-noltari-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-04-11 19:33 ` Rob Herring
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=1456054881-26787-1-git-send-email-noltari@gmail.com \
--to=noltari@gmail.com \
--cc=cernekee@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=jogo@openwrt.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--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 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).