Support for Fujitsu MB86S7X SoCs
Subsystems (7)
v4 cover Support for Fujitsu MB86S7X SoCs
Hello,
Fujitsu have a series of SoC already shipping based around
variations of 2xCA7+2xCA15 big.LITTLE architecture, and we would like to upstream the basic support in this series.
MB86S70 is a big.LITTLE platform with 2xCA7+2xCA15 and an additional
CM3 as the master. MB86S73 is a simple 2xCA7 and an additional CM3 master.
The DT includes references to sdhci patches which are being sent to
the mmc list at the same time.
We welcome any comments or questions.
Changes since v3:
* Identify platform, by checking presence of DT node "fujitsu,mb86s70-scb-1.0" before populating cpu clocks and MCPM support.
* Disable clock upon gpio module remove
* Lower init level of gpio driver from subsys_initcall to module_init
* Use managed device resource allocation in MHU driver
Changes since v2:
* Minor cleanup of MCPM as suggested by Nicolas Pitre.
Changes since v1:
* Thanks to Arnd, modified clock driver to populate clocks only when some user need them. Node name changed from "fujitsu,mb86s70-clk" to "fujitsu,mb86s70-crg11" . Controller+Domain+Port of a clock are now three cells specified by the user node.
* aliases moved into board DTS files
* Voltage supply moved as per-board DT node.
* Removed default overly verbose loglevel=8
* Specify -march=armv7-a flag for mcpm.c and smc.S that contain ARMv7 specific code.
* Removed wrongly put outer_flush_all(), now using standard v7_exit_coherency_flush() instead of platform specific macro.
* Simplified GPIO offset calculations in gpio-mb86s70.c driver. And added .remove() for the driver
* ARM MHU driver provided a .remove() to enable module unloading.
* A few other misc cleanups suggested in v1 submission.
Thanks.
Jassi Brar (8):
ARM: Add platform support for Fujitsu MB86S7X SoCs
mailbox: arm_mhu: add driver for ARM MHU controller
ARM: MB86S7X: Add MCPM support
clk: Add clock driver for mb86s7x
gpio: Add Fujitsu MB86S7x GPIO driver
dt: mb86s7x: add dt files for MB86S7x evbs
of: add Fujitsu vendor prefix
ARM: MB86S7x: Add configs
Documentation/devicetree/bindings/arm/mb86s7x.txt | 8 + .../bindings/clock/fujitsu,mb86s70-crg11.txt | 26 + .../bindings/gpio/fujitsu,mb86s70-gpio.txt | 20 + .../devicetree/bindings/mailbox/arm-mhu.txt | 33 ++ .../devicetree/bindings/soc/mb86s7x/scb_mhu.txt | 35 ++ .../devicetree/bindings/vendor-prefixes.txt | 1 + MAINTAINERS | 7 + arch/arm/Kconfig | 2 + arch/arm/Makefile | 1 + arch/arm/boot/dts/Makefile | 1 + arch/arm/boot/dts/mb86s70.dtsi | 91 ++++ arch/arm/boot/dts/mb86s70eb.dts | 57 +++ arch/arm/boot/dts/mb86s73.dtsi | 63 +++ arch/arm/boot/dts/mb86s73eb.dts | 44 ++ arch/arm/boot/dts/mb86s7x.dtsi | 140 ++++++ arch/arm/configs/fujitsu_defconfig | 232 +++++++++ arch/arm/configs/multi_v7_defconfig | 5 + arch/arm/mach-mb86s7x/Kconfig | 19 + arch/arm/mach-mb86s7x/Makefile | 3 + arch/arm/mach-mb86s7x/board.c | 23 + arch/arm/mach-mb86s7x/mcpm.c | 318 +++++++++++++ arch/arm/mach-mb86s7x/smc.S | 27 ++ drivers/clk/Makefile | 1 + drivers/clk/clk-mb86s7x.c | 386 +++++++++++++++ drivers/gpio/Kconfig | 6 + drivers/gpio/Makefile | 1 + drivers/gpio/gpio-mb86s7x.c | 232 +++++++++ drivers/mailbox/Kconfig | 7 + drivers/mailbox/Makefile | 2 + drivers/mailbox/arm_mhu.c | 211 ++++++++ drivers/soc/Makefile | 1 + drivers/soc/mb86s7x/Makefile | 4 + drivers/soc/mb86s7x/scb_mhu.c | 528 +++++++++++++++++++++ include/soc/mb86s7x/scb_mhu.h | 105 ++++ 34 files changed, 2640 insertions(+) create mode 100644 Documentation/devicetree/bindings/arm/mb86s7x.txt create mode 100644 Documentation/devicetree/bindings/clock/fujitsu,mb86s70-crg11.txt create mode 100644 Documentation/devicetree/bindings/gpio/fujitsu,mb86s70-gpio.txt create mode 100644 Documentation/devicetree/bindings/mailbox/arm-mhu.txt create mode 100644 Documentation/devicetree/bindings/soc/mb86s7x/scb_mhu.txt create mode 100644 arch/arm/boot/dts/mb86s70.dtsi create mode 100644 arch/arm/boot/dts/mb86s70eb.dts create mode 100644 arch/arm/boot/dts/mb86s73.dtsi create mode 100644 arch/arm/boot/dts/mb86s73eb.dts create mode 100644 arch/arm/boot/dts/mb86s7x.dtsi create mode 100644 arch/arm/configs/fujitsu_defconfig create mode 100644 arch/arm/mach-mb86s7x/Kconfig create mode 100644 arch/arm/mach-mb86s7x/Makefile create mode 100644 arch/arm/mach-mb86s7x/board.c create mode 100644 arch/arm/mach-mb86s7x/mcpm.c create mode 100644 arch/arm/mach-mb86s7x/smc.S create mode 100644 drivers/clk/clk-mb86s7x.c create mode 100644 drivers/gpio/gpio-mb86s7x.c create mode 100644 drivers/mailbox/arm_mhu.c create mode 100644 drivers/soc/mb86s7x/Makefile create mode 100644 drivers/soc/mb86s7x/scb_mhu.c create mode 100644 include/soc/mb86s7x/scb_mhu.h
Signature · 1 line
1.9.0
PATCH v4 1/8 ARM: Add platform support for Fujitsu MB86S7X SoCs
From: Jassi Brar <[email protected]>
The MB86S7X is a bigLITTLE configuration of 2xCA7 & 2xCA15 under Linux. And the remote master firmware (called SCB) running on CM3. Linux asks for things to be done over Mailbox API, to SCB which controls most of the important things. variations S70 & S73 are supported.
--- Documentation/devicetree/bindings/arm/mb86s7x.txt | 8 + .../devicetree/bindings/soc/mb86s7x/scb_mhu.txt | 35 ++ MAINTAINERS | 7 + arch/arm/Kconfig | 2 + arch/arm/Makefile | 1 + arch/arm/mach-mb86s7x/Kconfig | 19 + arch/arm/mach-mb86s7x/Makefile | 1 + arch/arm/mach-mb86s7x/board.c | 23 + drivers/soc/Makefile | 1 + drivers/soc/mb86s7x/Makefile | 4 + drivers/soc/mb86s7x/scb_mhu.c | 514 +++++++++++++++++++++ include/soc/mb86s7x/scb_mhu.h | 97 ++++ 12 files changed, 712 insertions(+) create mode 100644 Documentation/devicetree/bindings/arm/mb86s7x.txt create mode 100644 Documentation/devicetree/bindings/soc/mb86s7x/scb_mhu.txt create mode 100644 arch/arm/mach-mb86s7x/Kconfig create mode 100644 arch/arm/mach-mb86s7x/Makefile create mode 100644 arch/arm/mach-mb86s7x/board.c create mode 100644 drivers/soc/mb86s7x/Makefile create mode 100644 drivers/soc/mb86s7x/scb_mhu.c create mode 100644 include/soc/mb86s7x/scb_mhu.h
Documentation/devicetree/bindings/arm/mb86s7x.txt new file +8 -0
@@ -0,0 +1,8 @@ +Fujitsu MB86S7X Device Tree Bindings + +Fujitsu has a few closely related platforms that are basically different +configurations of each others. Like MB86S7{0,1,2,3}. + +The EVB boards with S70/S73 have the following property: +Required root node property: + compatible: must contain "fujitsu,mb86s70-evb" or "fujitsu,mb86s73-evb"
Documentation/devicetree/bindings/soc/mb86s7x/scb_mhu.txt new file +35 -0
@@ -0,0 +1,35 @@ +Fujitsu SCB (Mailbox's Remote Firmware) bindings +------------------------------------------------ + +The firmware (running of a remote Cortex-M3 master) on Fujitsu's MB86S7X +platforms is named SCB. The SCB owns most of core h/w IPs like Clock, +CPUFreq/DVFS, CPUIdle/SMP, Thermal, a recovery block device and even an +I2C controller. Linux has to map all of these functionalities on to +the Mailbox API and get things done by the remote master. + Let the current state of SCB firmware be versioned 1.0. + +Required properties : +- compatible : Shall contain "fujitsu,mb86s70-scb-1.0" +- reg : Point to SharedMemory used for Mailbox protocol. +- mboxes : phandle to the mailbox controller:channel node. + +The consumer specifies the desired clock pointing to its phandle. + +Example: + + mhu: mhu0 at 2b1f0000 { + #mbox-cells = <1>; + compatible = "arm,mbox-mhu"; + reg = <0 0x2b1f0000 0x1000>; + interrupts = <0 36 4>, /* LP Non-Sec */ + <0 35 4>, /* HP Non-Sec */ + <0 37 4>; /* Secure */ + clocks = <&clk 0 2 1>; + clock-names = "clk"; + }; + + mhu_client: scb at 2e000000 { + compatible = "fujitsu,mb86s70-scb-1.0"; + reg = <0 0x2e000000 0x4000>; /* SHM for IPC */ + mboxes = <&mhu 1>; + };
MAINTAINERS +7 -0
@@ -1108,6 +1108,13 @@ M: Lennert Buytenhek <[email protected]> L: linux-arm-kernel at lists.infradead.org (moderated for non-subscribers) S: Maintained +ARM/MB86S7X SOC SUPPORT +M: Vincent Yang <[email protected]> +M: Tetsuya Nuriya <[email protected]> +L: linux-arm-kernel at lists.infradead.org (moderated for non-subscribers) +S: Supported +F: arch/arm/mach-mb86s7x/ + ARM/TEXAS INSTRUMENT KEYSTONE ARCHITECTURE M: Santosh Shilimkar <[email protected]> L: linux-arm-kernel at lists.infradead.org (moderated for non-subscribers)
arch/arm/Kconfig +2 -0
@@ -884,6 +884,8 @@ source "arch/arm/mach-keystone/Kconfig" source "arch/arm/mach-ks8695/Kconfig" +source "arch/arm/mach-mb86s7x/Kconfig" + source "arch/arm/mach-meson/Kconfig" source "arch/arm/mach-msm/Kconfig"
arch/arm/Makefile +1 -0
@@ -167,6 +167,7 @@ machine-$(CONFIG_ARCH_IXP4XX) += ixp4xx machine-$(CONFIG_ARCH_KEYSTONE) += keystone machine-$(CONFIG_ARCH_KS8695) += ks8695 machine-$(CONFIG_ARCH_LPC32XX) += lpc32xx +machine-$(CONFIG_ARCH_MB86S7X) += mb86s7x machine-$(CONFIG_ARCH_MESON) += meson machine-$(CONFIG_ARCH_MMP) += mmp machine-$(CONFIG_ARCH_MOXART) += moxart
arch/arm/mach-mb86s7x/Kconfig new file +19 -0
@@ -0,0 +1,19 @@ +config ARCH_MB86S7X + bool "Fujitsu MB86S7x platforms" if ARCH_MULTI_V7 + select ARCH_DMA_ADDR_T_64BIT if ARM_LPAE + select ARCH_HAS_CPUFREQ + select ARCH_HAS_OPP + select ARCH_REQUIRE_GPIOLIB + select ARM_AMBA + select ARM_CCI + select ARM_GIC + select ARM_TIMER_SP804 + select BIG_LITTLE + select HAVE_ARM_ARCH_TIMER + select MAILBOX + select PINCTRL + select PINCTRL_MB86S7X + select PM_OPP + select ZONE_DMA if ARM_LPAE + help + Support for Fujitsu MB86S7x based platforms
arch/arm/mach-mb86s7x/Makefile new file +1 -0
@@ -0,0 +1 @@ +obj-$(CONFIG_ARCH_MB86S7X) += board.o
arch/arm/mach-mb86s7x/board.c new file +23 -0
@@ -0,0 +1,23 @@ +/* +* Support for the Fujitsu's MB86S7x based devices. +* +* Copyright (C) 2015 Linaro, LTD +* +* This program is free software: you can redistribute it and/or modify +* it under the terms of the GNU General Public License as published by +* the Free Software Foundation, version 2 of the License. +* +*/ + +#include <linux/of.h> +#include <asm/mach/arch.h> + +static const char *mb86s7x_dt_match[]__initconst = { +"fujitsu,mb86s70-evb" , +"fujitsu,mb86s73-evb" , +NULL , +}; + +DT_MACHINE_START (MB86S7X_DT ,"Fujitsu MB86S7X-based board" ) + .dt_compat = mb86s7x_dt_match, +MACHINE_END
drivers/soc/Makefile +1 -0
@@ -2,6 +2,7 @@ # Makefile for the Linux Kernel SOC specific device drivers. # +obj-$(CONFIG_ARCH_MB86S7X) += mb86s7x/ obj-$(CONFIG_ARCH_QCOM) += qcom/ obj-$(CONFIG_ARCH_TEGRA) += tegra/ obj-$(CONFIG_SOC_TI) += ti/
drivers/soc/mb86s7x/Makefile new file +4 -0
@@ -0,0 +1,4 @@ +# +# Fujitsu's MB86S7X drivers +# +obj-$(CONFIG_ARCH_MB86S7X) += scb_mhu.o
drivers/soc/mb86s7x/scb_mhu.c new file +514 -0
514 lines not on this page · raw message
include/soc/mb86s7x/scb_mhu.h new file +97 -0
97 lines not on this page · raw message
Signature · 1 line
1.9.0
PATCH v4 2/8 mailbox: arm_mhu: add driver for ARM MHU controller
In reply to Vincent YangFrom: Jassi Brar <[email protected]>
Add driver for the ARM Message-Handling-Unit (MHU).
--- .../devicetree/bindings/mailbox/arm-mhu.txt | 33 ++++ drivers/mailbox/Kconfig | 7 + drivers/mailbox/Makefile | 2 + drivers/mailbox/arm_mhu.c | 211 +++++++++++++++++++++ 4 files changed, 253 insertions(+) create mode 100644 Documentation/devicetree/bindings/mailbox/arm-mhu.txt create mode 100644 drivers/mailbox/arm_mhu.c
Documentation/devicetree/bindings/mailbox/arm-mhu.txt new file +33 -0
@@ -0,0 +1,33 @@ +ARM MHU Mailbox Driver +====================== + +The ARM's Message-Handling-Unit (MHU) is a mailbox controller that has +3 independent channels/links to communicate with remote processor(s). + MHU links are hardwired on a platform. A link raises interrupt for any +received data. However, there is no specified way of knowing if the sent +data has been read by the remote. This driver assumes the sender polls +STAT register and the remote clears it after having read the data. + +Mailbox Device Node: +==================== + +Required properties: +-------------------- +- compatible: Shall be "arm,mbox-mhu" +- reg: Contains the mailbox register address range (base + address and length) +- #mbox-cells Shall be 1 +- interrupts: Contains the interrupt information corresponding to + each of the 3 links of MHU. + +Example: +-------- + + mhu: mailbox at 2b1f0000 { + #mbox-cells = <1>; + compatible = "arm,mbox-mhu"; + reg = <0 0x2b1f0000 0x1000>; + interrupts = <0 36 4>, + <0 35 4>, + <0 37 4>; + };
drivers/mailbox/Kconfig +7 -0
@@ -6,6 +6,13 @@ menuconfig MAILBOX signals. Say Y if your platform supports hardware mailboxes. if MAILBOX + +config ARM_MHU + tristate "ARM MHU Mailbox" + depends on ARM + help + Say Y here if you want to build the ARM MHU controller driver + config PL320_MBOX bool "ARM PL320 Mailbox" depends on ARM_AMBA
drivers/mailbox/Makefile +2 -0
@@ -2,6 +2,8 @@ obj-$(CONFIG_MAILBOX) += mailbox.o +obj-$(CONFIG_ARM_MHU) += arm_mhu.o + obj-$(CONFIG_PL320_MBOX) += pl320-ipc.o obj-$(CONFIG_OMAP2PLUS_MBOX) += omap-mailbox.o
drivers/mailbox/arm_mhu.c new file +211 -0
211 lines not on this page · raw message
Signature · 1 line
1.9.0
PATCH v4 2/8 mailbox: arm_mhu: add driver for ARM MHU controller
Quoted 3 lines · Vincent Yang
From: Jassi Brar <[email protected]>
Add driver for the ARM Message-Handling-Unit (MHU).
Is this an AMBA Primecell peripheral? If so, it should not be a platform driver.
Thanks.
Signature · 2 lines
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up according to speedtest.net.
PATCH v4 2/8 mailbox: arm_mhu: add driver for ARM MHU controller
Quoted 8 lines · Russell King - ARM Linux
Quoted 3 lines · Vincent Yang
From: Jassi Brar <[email protected]>
Add driver for the ARM Message-Handling-Unit (MHU).
Is this an AMBA Primecell peripheral? If so, it should not be a platform driver.
Yes, it is. We have revised the driver and should be part of the revised patchset to be submitted shortly.
Thank you.
PATCH v4 3/8 ARM: MB86S7X: Add MCPM support
In reply to Vincent YangFrom: Jassi Brar <[email protected]>
The remote firmware(SCB) owns the SMP control. This MCPM driver gets CPU/CLUSTER power up/down done by SCB over mailbox.
--- arch/arm/mach-mb86s7x/Makefile | 4 +- arch/arm/mach-mb86s7x/mcpm.c | 318 +++++++++++++++++++++++++++++++++++++++++ arch/arm/mach-mb86s7x/smc.S | 27 ++++ drivers/soc/mb86s7x/scb_mhu.c | 14 ++ include/soc/mb86s7x/scb_mhu.h | 8 ++ 5 files changed, 370 insertions(+), 1 deletion(-) create mode 100644 arch/arm/mach-mb86s7x/mcpm.c create mode 100644 arch/arm/mach-mb86s7x/smc.S
arch/arm/mach-mb86s7x/Makefile +3 -1
@@ -1 +1,3 @@ -obj-$(CONFIG_ARCH_MB86S7X) += board.o +obj-$(CONFIG_ARCH_MB86S7X) += board.o mcpm.o smc.o +CFLAGS_smc.o += -march=armv7-a +CFLAGS_mcpm.o += -march=armv7-a
arch/arm/mach-mb86s7x/mcpm.c new file +318 -0
318 lines not on this page · raw message
arch/arm/mach-mb86s7x/smc.S new file +27 -0
@@ -0,0 +1,27 @@ +/* + * SMC command interface to set secondary entry point + * Copyright: (C) 2013-2015 Fujitsu Semiconductor Limited + * Copyright: (C) 2015 Linaro Ltd. + * + * This program is free software; you can redistribute it and/or modify + * it under the terms of the GNU General Public License version 2 as + * published by the Free Software Foundation. + */ + +#include <linux/linkage.h> + +.arch_extension sec + +/* void mb86s7x_cpu_entry(unsigned long secondary_entry); */ +ENTRY(mb86s7x_cpu_entry) + stmfd sp!, {r1-r11, lr} + mov r1, r0 + ldr r0, =1 + mrc p15, 0, r3, c1, c0, 0 + mov r4, r3 + and r3, #0xbfffffff + mcr p15, 0, r3, c1, c0, 0 + smc #0 + mcr p15, 0, r4, c1, c0, 0 + ldmfd sp!, {r1-r11, pc} +ENDPROC(mb86s7x_cpu_entry)
drivers/soc/mb86s7x/scb_mhu.c +14 -0
@@ -89,6 +89,20 @@ static struct mhu_xfer {struct list_head node; } *ax;/* stages of xfer */ +#define WFI_COLOR_OFFSET 0x3f00 + +void mb86s7x_set_wficolor (unsigned clstr,unsigned cpu,unsigned clr) +{ +u8 val; + + val =readb_relaxed (mb86s7x_shm_base + +WFI_COLOR_OFFSET + clstr *2 + cpu); + val &= ~AT_WFI_COLOR_MASK ; + val |= clr; +writeb_relaxed (val, mb86s7x_shm_base + +WFI_COLOR_OFFSET + clstr *2 + cpu); +} +static int mhu_alloc_xfers (int n,struct list_head *list) {struct mhu_xfer *x =kcalloc (n,sizeof (struct mhu_xfer ),GFP_ATOMIC );
include/soc/mb86s7x/scb_mhu.h +8 -0
@@ -87,6 +87,14 @@ enum {#define CMD_POWERDOMAIN_SET_REP ENC_REP(CMD_POWERDOMAIN_SET_REQ)#define CMD_STG_BLOCK_ERASE_REP ENC_REP(CMD_STG_BLOCK_ERASE_REQ) +#define AT_WFI_DO_NOTHING 0x0 +#define AT_WFI_DO_SUSPEND 0x1 +#define AT_WFI_DO_POWEROFF 0x2 +#define AT_WFI_COLOR_MASK 0x3 + +void mb86s7x_set_wficolor (unsigned clstr,unsigned cpu,unsigned clr); +void mb86s7x_cpu_entry (unsigned long secondary_entry); +/* Helper functions to talk to remote */ int mb86s7x_send_packet (int cmd,void *buf,int len);
Signature · 1 line
1.9.0
PATCH v4 4/8 clk: Add clock driver for mb86s7x
In reply to Vincent YangFrom: Jassi Brar <[email protected]>
The CRG11 clock controller is managed by remote f/w.
This driver simply maps Linux CLK ops onto mailbox api.
--- .../bindings/clock/fujitsu,mb86s70-crg11.txt | 26 ++ drivers/clk/Makefile | 1 + drivers/clk/clk-mb86s7x.c | 386 +++++++++++++++++++++ 3 files changed, 413 insertions(+) create mode 100644 Documentation/devicetree/bindings/clock/fujitsu,mb86s70-crg11.txt create mode 100644 drivers/clk/clk-mb86s7x.c
Documentation/devicetree/bindings/clock/fujitsu,mb86s70-crg11.txt new file +26 -0
@@ -0,0 +1,26 @@ +Fujitsu CRG11 clock driver bindings +----------------------------------- + +Required properties : +- compatible : Shall contain "fujitsu,mb86s70-crg11" +- #clock-cells : Shall be 3 {cntrlr domain port} + +The consumer specifies the desired clock pointing to its phandle. + +Example: + + clock: crg11 { + compatible = "fujitsu,mb86s70-crg11"; + #clock-cells = <3>; + }; + + mhu: mhu0 at 2b1f0000 { + #mbox-cells = <1>; + compatible = "arm,mbox-mhu"; + reg = <0 0x2B1F0000 0x1000>; + interrupts = <0 36 4>, /* LP Non-Sec */ + <0 35 4>, /* HP Non-Sec */ + <0 37 4>; /* Secure */ + clocks = <&clock 0 2 1>; /* Cntrlr:0 Domain:2 Port:1 */ + clock-names = "clk"; + };
drivers/clk/Makefile +1 -0
@@ -26,6 +26,7 @@ obj-$(CONFIG_MACH_LOONGSON1) += clk-ls1x.o obj-$(CONFIG_COMMON_CLK_MAX_GEN) += clk-max-gen.o obj-$(CONFIG_COMMON_CLK_MAX77686) += clk-max77686.o obj-$(CONFIG_COMMON_CLK_MAX77802) += clk-max77802.o +obj-$(CONFIG_ARCH_MB86S7X) += clk-mb86s7x.o obj-$(CONFIG_ARCH_MOXART) += clk-moxart.o obj-$(CONFIG_ARCH_NOMADIK) += clk-nomadik.o obj-$(CONFIG_ARCH_NSPIRE) += clk-nspire.o
drivers/clk/clk-mb86s7x.c new file +386 -0
386 lines not on this page · raw message
Signature · 1 line
1.9.0
PATCH v4 5/8 gpio: Add Fujitsu MB86S7x GPIO driver
In reply to Vincent YangFrom: Jassi Brar <[email protected]>
Driver for Fujitsu MB86S7x SoCs that have a memory mapped GPIO controller.
--- .../bindings/gpio/fujitsu,mb86s70-gpio.txt | 20 ++ drivers/gpio/Kconfig | 6 + drivers/gpio/Makefile | 1 + drivers/gpio/gpio-mb86s7x.c | 232 +++++++++++++++++++++ 4 files changed, 259 insertions(+) create mode 100644 Documentation/devicetree/bindings/gpio/fujitsu,mb86s70-gpio.txt create mode 100644 drivers/gpio/gpio-mb86s7x.c
Documentation/devicetree/bindings/gpio/fujitsu,mb86s70-gpio.txt new file +20 -0
@@ -0,0 +1,20 @@ +Fujitsu MB86S7x GPIO Controller +------------------------------- + +Required properties: +- compatible: Should be "fujitsu,mb86s70-gpio" +- reg: Base address and length of register space +- clocks: Specify the clock +- gpio-controller: Marks the device node as a gpio controller. +- #gpio-cells: Should be <2>. The first cell is the pin number and the + second cell is used to specify optional parameters: + - bit 0 specifies polarity (0 for normal, 1 for inverted). + +Examples: + gpio0: gpio at 31000000 { + compatible = "fujitsu,mb86s70-gpio"; + reg = <0 0x31000000 0x10000>; + gpio-controller; + #gpio-cells = <2>; + clocks = <&clk 0 2 1>; + };
drivers/gpio/Kconfig +6 -0
@@ -197,6 +197,12 @@ config GPIO_F7188X To compile this driver as a module, choose M here: the module will be called f7188x-gpio. +config GPIO_MB86S7X + bool "GPIO support for Fujitsu MB86S7x Platforms" + depends on ARCH_MB86S7X + help + Say yes here to support the GPIO controller in Fujitsu MB86S70 SoCs. + config GPIO_MOXART bool "MOXART GPIO support" depends on ARCH_MOXART
drivers/gpio/Makefile +1 -0
@@ -48,6 +48,7 @@ obj-$(CONFIG_GPIO_MAX730X) += gpio-max730x.o obj-$(CONFIG_GPIO_MAX7300) += gpio-max7300.o obj-$(CONFIG_GPIO_MAX7301) += gpio-max7301.o obj-$(CONFIG_GPIO_MAX732X) += gpio-max732x.o +obj-$(CONFIG_GPIO_MB86S7X) += gpio-mb86s7x.o obj-$(CONFIG_GPIO_MC33880) += gpio-mc33880.o obj-$(CONFIG_GPIO_MC9S08DZ60) += gpio-mc9s08dz60.o obj-$(CONFIG_GPIO_MCP23S08) += gpio-mcp23s08.o
drivers/gpio/gpio-mb86s7x.c new file +232 -0
232 lines not on this page · raw message
Signature · 1 line
1.9.0
PATCH v4 5/8 gpio: Add Fujitsu MB86S7x GPIO driver
Quoted 8 lines · Vincent Yang
From: Jassi Brar <[email protected]>
Driver for Fujitsu MB86S7x SoCs that have a memory mapped GPIO controller.
Signed-off-by Jassi Brar <[email protected]>Signed-off-by Andy Green <[email protected]>Signed-off-by Vincent Yang <[email protected]>Signed-off-by Tetsuya Nuriya <[email protected]>
Looking good and I now understand everything about this driver, patch applied! (And thanks for your patience.)
Yours,
Linus Walleij
PATCH v4 6/8 dt: mb86s7x: add dt files for MB86S7x evbs
In reply to Vincent YangFrom: Jassi Brar <[email protected]>
Add dt files for MB86S7x evb.
--- arch/arm/boot/dts/Makefile | 1 + arch/arm/boot/dts/mb86s70.dtsi | 91 ++++++++++++++++++++++++++ arch/arm/boot/dts/mb86s70eb.dts | 57 ++++++++++++++++ arch/arm/boot/dts/mb86s73.dtsi | 63 ++++++++++++++++++ arch/arm/boot/dts/mb86s73eb.dts | 44 +++++++++++++ arch/arm/boot/dts/mb86s7x.dtsi | 140 ++++++++++++++++++++++++++++++++++++++++ 6 files changed, 396 insertions(+) create mode 100644 arch/arm/boot/dts/mb86s70.dtsi create mode 100644 arch/arm/boot/dts/mb86s70eb.dts create mode 100644 arch/arm/boot/dts/mb86s73.dtsi create mode 100644 arch/arm/boot/dts/mb86s73eb.dts create mode 100644 arch/arm/boot/dts/mb86s7x.dtsi
arch/arm/boot/dts/Makefile +1 -0
@@ -176,6 +176,7 @@ dtb-$(CONFIG_MACH_KIRKWOOD) += kirkwood-b3.dtb \ kirkwood-ts419-6282.dtb dtb-$(CONFIG_ARCH_LPC32XX) += ea3250.dtb phy3250.dtb dtb-$(CONFIG_ARCH_MARCO) += marco-evb.dtb +dtb-$(CONFIG_ARCH_MB86S7X) += mb86s70eb.dtb mb86s73eb.dtb dtb-$(CONFIG_MACH_MESON6) += meson6-atv1200.dtb dtb-$(CONFIG_ARCH_MMP) += pxa168-aspenite.dtb \ pxa910-dkb.dtb \
arch/arm/boot/dts/mb86s70.dtsi new file +91 -0
91 lines not on this page · raw message
arch/arm/boot/dts/mb86s70eb.dts new file +57 -0
57 lines not on this page · raw message
arch/arm/boot/dts/mb86s73.dtsi new file +63 -0
63 lines not on this page · raw message
arch/arm/boot/dts/mb86s73eb.dts new file +44 -0
44 lines not on this page · raw message
arch/arm/boot/dts/mb86s7x.dtsi new file +140 -0
140 lines not on this page · raw message
Signature · 1 line
1.9.0
PATCH v4 7/8 of: add Fujitsu vendor prefix
In reply to Vincent YangFrom: Jassi Brar <[email protected]>
Add 'fujitsu' as the vendor prefix for Fujitsu Semiconductor Ltd.
--- Documentation/devicetree/bindings/vendor-prefixes.txt | 1 + 1 file changed, 1 insertion(+)
Documentation/devicetree/bindings/vendor-prefixes.txt +1 -0
@@ -59,6 +59,7 @@ everest Everest Semiconductor Co. Ltd. excito Excito fcs Fairchild Semiconductor fsl Freescale Semiconductor +fujitsu Fujitsu Semiconductor Ltd. GEFanuc GE Fanuc Intelligent Platforms Embedded Systems, Inc. gef GE Fanuc Intelligent Platforms Embedded Systems, Inc. geniatech Geniatech, Inc.
Signature · 1 line
1.9.0
PATCH v4 8/8 ARM: MB86S7x: Add configs
In reply to Vincent YangFrom: Jassi Brar <[email protected]>
Fujitsu's ARCH_MB86S7X is multi_v7 compatible, so add options to multi_v7_defconfig. Also add a new defconfig for MB86S7X for those who want the kernel built specifically for ARCH_MB86S7X.
--- arch/arm/configs/fujitsu_defconfig | 232 ++++++++++++++++++++++++++++++++++++ arch/arm/configs/multi_v7_defconfig | 5 + 2 files changed, 237 insertions(+) create mode 100644 arch/arm/configs/fujitsu_defconfig
arch/arm/configs/fujitsu_defconfig new file +232 -0
@@ -0,0 +1,232 @@ +# CONFIG_LOCALVERSION_AUTO is not set +CONFIG_DEFAULT_HOSTNAME="MB86S7x" +CONFIG_SYSVIPC=y +CONFIG_POSIX_MQUEUE=y +CONFIG_NO_HZ=y +CONFIG_HIGH_RES_TIMERS=y +CONFIG_IKCONFIG=y +CONFIG_IKCONFIG_PROC=y +CONFIG_NAMESPACES=y +CONFIG_BLK_DEV_INITRD=y +CONFIG_RD_BZIP2=y +CONFIG_RD_LZMA=y +CONFIG_RD_XZ=y +CONFIG_RD_LZO=y +CONFIG_CC_OPTIMIZE_FOR_SIZE=y +CONFIG_EXPERT=y +# CONFIG_COMPAT_BRK is not set +CONFIG_SLAB=y +CONFIG_PROFILING=y +CONFIG_MODULES=y +CONFIG_MODULE_UNLOAD=y +CONFIG_ARCH_MB86S7X=y +CONFIG_ARM_LPAE=y +CONFIG_ARM_ERRATA_754322=y +CONFIG_ARM_ERRATA_754327=y +CONFIG_ARM_ERRATA_764369=y +CONFIG_ARM_ERRATA_775420=y +CONFIG_ARM_ERRATA_798181=y +CONFIG_PCI=y +CONFIG_SMP=y +CONFIG_SCHED_MC=y +CONFIG_SCHED_SMT=y +CONFIG_VMSPLIT_2G=y +CONFIG_PREEMPT=y +CONFIG_THUMB2_KERNEL=y +CONFIG_HIGHMEM=y +CONFIG_CMA=y +CONFIG_CMA_AREAS=8 +# CONFIG_ATAGS is not set +CONFIG_ZBOOT_ROM_TEXT=0x0 +CONFIG_ZBOOT_ROM_BSS=0x0 +CONFIG_CMDLINE="mem=2048M console=ttyS0,115200 root=/dev/mmcblk1p1 rootfstype=ext4 rootwait rw" +CONFIG_KEXEC=y +CONFIG_CPU_FREQ=y +CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y +CONFIG_CPUFREQ_DT=m +CONFIG_CPU_IDLE=y +CONFIG_VFP=y +CONFIG_NEON=y +CONFIG_PM_WAKELOCKS=y +CONFIG_PM_RUNTIME=y +CONFIG_PM_DEBUG=y +CONFIG_NET=y +CONFIG_PACKET=y +CONFIG_UNIX=y +CONFIG_INET=y +CONFIG_IP_MULTICAST=y +CONFIG_IP_PNP=y +CONFIG_IP_PNP_DHCP=y +CONFIG_IP_PNP_BOOTP=y +# CONFIG_INET_XFRM_MODE_TRANSPORT is not set +# CONFIG_INET_XFRM_MODE_TUNNEL is not set +# CONFIG_INET_XFRM_MODE_BEET is not set +# CONFIG_INET_LRO is not set +# CONFIG_IPV6 is not set +# CONFIG_WIRELESS is not set +CONFIG_DEVTMPFS=y +CONFIG_DEVTMPFS_MOUNT=y +CONFIG_DMA_CMA=y +CONFIG_CMA_SIZE_MBYTES=192 +CONFIG_MTD=y +CONFIG_MTD_CMDLINE_PARTS=y +CONFIG_MTD_BLOCK=y +CONFIG_MTD_CFI=y +CONFIG_MTD_CFI_ADV_OPTIONS=y +CONFIG_MTD_CFI_AMDSTD=y +CONFIG_MTD_ROM=y +CONFIG_MTD_COMPLEX_MAPPINGS=y +CONFIG_MTD_PHYSMAP=y +CONFIG_MTD_PHYSMAP_OF=y +CONFIG_MTD_PLATRAM=y +CONFIG_MTD_M25P80=y +CONFIG_MTD_SPI_NOR=y +CONFIG_BLK_DEV_LOOP=m +CONFIG_BLK_DEV_CRYPTOLOOP=m +CONFIG_BLK_DEV_RAM=y +CONFIG_BLK_DEV_RAM_COUNT=2 +CONFIG_BLK_DEV_RAM_SIZE=1024 +CONFIG_BLK_DEV_SD=m +CONFIG_ATA=m +# CONFIG_ATA_VERBOSE_ERROR is not set +# CONFIG_SATA_PMP is not set +CONFIG_SATA_AHCI_PLATFORM=m +# CONFIG_ATA_SFF is not set +CONFIG_NETDEVICES=y +CONFIG_TUN=m +# CONFIG_NET_CADENCE is not set +# CONFIG_NET_VENDOR_BROADCOM is not set +# CONFIG_NET_VENDOR_CIRRUS is not set +# CONFIG_NET_VENDOR_FARADAY is not set +# CONFIG_NET_VENDOR_INTEL is not set +# CONFIG_NET_VENDOR_MARVELL is not set +# CONFIG_NET_VENDOR_MICREL is not set +# CONFIG_NET_VENDOR_MICROCHIP is not set +# CONFIG_NET_VENDOR_NATSEMI is not set +# CONFIG_NET_VENDOR_SEEQ is not set +# CONFIG_NET_VENDOR_SMSC is not set +# CONFIG_NET_VENDOR_STMICRO is not set +# CONFIG_NET_VENDOR_WIZNET is not set +CONFIG_PHYLIB=y +# CONFIG_WLAN is not set +# CONFIG_INPUT_MOUSEDEV_PSAUX is not set +CONFIG_INPUT_MOUSEDEV_SCREEN_X=800 +CONFIG_INPUT_MOUSEDEV_SCREEN_Y=480 +CONFIG_INPUT_EVDEV=m +# CONFIG_KEYBOARD_ATKBD is not set +CONFIG_KEYBOARD_GPIO_POLLED=y +# CONFIG_MOUSE_PS2 is not set +CONFIG_MOUSE_GPIO=m +CONFIG_INPUT_TOUCHSCREEN=y +CONFIG_TOUCHSCREEN_EGALAX=m +CONFIG_TOUCHSCREEN_ILI210X=m +# CONFIG_SERIO_SERPORT is not set +CONFIG_LEGACY_PTY_COUNT=16 +# CONFIG_DEVKMEM is not set +CONFIG_SERIAL_8250=y +# CONFIG_SERIAL_8250_DEPRECATED_OPTIONS is not set +CONFIG_SERIAL_8250_CONSOLE=y +CONFIG_SERIAL_8250_EXTENDED=y +CONFIG_SERIAL_8250_DW=y +CONFIG_SERIAL_OF_PLATFORM=y +# CONFIG_HW_RANDOM is not set +# CONFIG_I2C_COMPAT is not set +CONFIG_I2C_CHARDEV=m +# CONFIG_I2C_HELPER_AUTO is not set +CONFIG_SPI=y +CONFIG_GPIO_SYSFS=y +CONFIG_GPIO_MB86S7X=y +CONFIG_GPIO_MCP23S08=m +# CONFIG_HWMON is not set +CONFIG_REGULATOR=y +CONFIG_REGULATOR_GPIO=y +# CONFIG_VGA_ARB is not set +CONFIG_DRM=y +CONFIG_FB=y +CONFIG_FIRMWARE_EDID=y +CONFIG_FB_MODE_HELPERS=y +CONFIG_FB_TILEBLITTING=y +CONFIG_BACKLIGHT_LCD_SUPPORT=y +CONFIG_FRAMEBUFFER_CONSOLE=y +CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y +CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y +CONFIG_LOGO=y +# CONFIG_LOGO_LINUX_MONO is not set +# CONFIG_LOGO_LINUX_VGA16 is not set +CONFIG_SOUND=m +CONFIG_SND=m +CONFIG_SND_DYNAMIC_MINORS=y +# CONFIG_SND_SUPPORT_OLD_API is not set +# CONFIG_SND_VERBOSE_PROCFS is not set +# CONFIG_SND_ARM is not set +# CONFIG_SND_SPI is not set +CONFIG_SND_SOC=m +CONFIG_HID=m +CONFIG_HID_PID=y +CONFIG_USB_HIDDEV=y +CONFIG_USB=m +CONFIG_USB_OTG=y +CONFIG_USB_XHCI_HCD=m +CONFIG_USB_EHCI_HCD=m +CONFIG_USB_EHCI_HCD_PLATFORM=m +CONFIG_USB_OHCI_HCD=m +# CONFIG_USB_OHCI_HCD_PCI is not set +CONFIG_USB_OHCI_HCD_PLATFORM=m +CONFIG_USB_ACM=m +CONFIG_USB_STORAGE=m +CONFIG_USB_DWC3=m +CONFIG_USB_DWC3_HOST=y +CONFIG_USB_DWC3_DEBUG=y +CONFIG_USB_GADGET=m +CONFIG_USB_MASS_STORAGE=m +CONFIG_USB_G_MULTI=m +CONFIG_MMC=y +CONFIG_MMC_CLKGATE=y +CONFIG_MMC_SDHCI=y +CONFIG_MMC_SDHCI_PLTFM=y +CONFIG_MMC_SDHCI_F_SDH30=y +CONFIG_NEW_LEDS=y +CONFIG_LEDS_CLASS=y +CONFIG_LEDS_GPIO=y +CONFIG_LEDS_TRIGGERS=y +CONFIG_LEDS_TRIGGER_TIMER=y +CONFIG_LEDS_TRIGGER_HEARTBEAT=y +CONFIG_LEDS_TRIGGER_BACKLIGHT=m +CONFIG_LEDS_TRIGGER_CPU=y +CONFIG_LEDS_TRIGGER_DEFAULT_ON=y +CONFIG_LEDS_TRIGGER_TRANSIENT=m +CONFIG_DMADEVICES=y +CONFIG_STAGING=y +CONFIG_ANDROID=y +CONFIG_ANDROID_BINDER_IPC=y +CONFIG_ASHMEM=y +CONFIG_ANDROID_LOGGER=m +CONFIG_ANDROID_LOW_MEMORY_KILLER=y +CONFIG_ION=y +CONFIG_ARM_MHU=y +CONFIG_ARM_SMMU=y +CONFIG_EXT4_FS=y +CONFIG_EXT4_FS_POSIX_ACL=y +CONFIG_EXT4_FS_SECURITY=y +CONFIG_VFAT_FS=m +CONFIG_TMPFS=y +CONFIG_JFFS2_FS=m +CONFIG_CRAMFS=y +CONFIG_ROMFS_FS=y +CONFIG_ROMFS_BACKED_BY_BOTH=y +# CONFIG_NETWORK_FILESYSTEMS is not set +CONFIG_NLS_CODEPAGE_437=m +CONFIG_NLS_ISO8859_1=m +CONFIG_PRINTK_TIME=y +CONFIG_DEBUG_INFO=y +CONFIG_DEBUG_FS=y +CONFIG_MAGIC_SYSRQ=y +CONFIG_DEBUG_MEMORY_INIT=y +# CONFIG_DEBUG_PREEMPT is not set +# CONFIG_RCU_CPU_STALL_VERBOSE is not set +# CONFIG_FTRACE is not set +CONFIG_DEBUG_USER=y +# CONFIG_CRYPTO_ANSI_CPRNG is not set +# CONFIG_CRYPTO_HW is not set +CONFIG_FONTS=y +CONFIG_FONT_SUN8x16=y
arch/arm/configs/multi_v7_defconfig +5 -0
@@ -49,6 +49,7 @@ CONFIG_SOC_AM43XX=y CONFIG_SOC_DRA7XX=y CONFIG_ARCH_QCOM=y CONFIG_ARCH_MEDIATEK=y +CONFIG_ARCH_MB86S7X=y CONFIG_ARCH_MSM8X60=y CONFIG_ARCH_MSM8960=y CONFIG_ARCH_MSM8974=y
@@ -259,6 +260,7 @@ CONFIG_GPIO_TWL4030=y CONFIG_GPIO_PALMAS=y CONFIG_GPIO_TPS6586X=y CONFIG_GPIO_TPS65910=y +CONFIG_GPIO_MB86S7X=y CONFIG_BATTERY_SBS=y CONFIG_CHARGER_TPS65090=y CONFIG_POWER_RESET_AS3722=y
@@ -370,6 +372,7 @@ CONFIG_MMC_SDHCI_SPEAR=y CONFIG_MMC_SDHCI_S3C=y CONFIG_MMC_SDHCI_S3C_DMA=y CONFIG_MMC_SDHCI_BCM_KONA=y +CONFIG_MMC_SDHCI_F_SDH30=y CONFIG_MMC_SDHCI_ST=y CONFIG_MMC_OMAP=y CONFIG_MMC_OMAP_HS=y
@@ -457,6 +460,8 @@ CONFIG_TI_PIPE3=y CONFIG_PHY_MIPHY365X=y CONFIG_PHY_STIH41X_USB=y CONFIG_PHY_SUN4I_USB=y +CONFIG_MAILBOX=y +CONFIG_ARM_MHU=y CONFIG_EXT4_FS=y CONFIG_AUTOFS4_FS=y CONFIG_MSDOS_FS=y
Signature · 1 line
1.9.0
v4 cover Support for Fujitsu MB86S7X SoCs
In reply to Vincent YangHi Arnd, Hi Olof,
... just a polite ping on the patchset.
Thanks.
Quoted 116 lines · Vincent Yang
Hello,
Fujitsu have a series of SoC already shipping based around
variations of 2xCA7+2xCA15 big.LITTLE architecture, and we would like to upstream the basic support in this series.MB86S70 is a big.LITTLE platform with 2xCA7+2xCA15 and an additional
CM3 as the master. MB86S73 is a simple 2xCA7 and an additional CM3 master.The DT includes references to sdhci patches which are being sent to
the mmc list at the same time.We welcome any comments or questions.
Changes since v3:
* Identify platform, by checking presence of DT node "fujitsu,mb86s70-scb-1.0" before populating cpu clocks and MCPM support.
* Disable clock upon gpio module remove
* Lower init level of gpio driver fromsubsys_initcalltomodule_init
* Use managed device resource allocation in MHU driverChanges since v2:
* Minor cleanup of MCPM as suggested by Nicolas Pitre.Changes since v1:
* Thanks to Arnd, modified clock driver to populate clocks only when some user need them. Node name changed from "fujitsu,mb86s70-clk" to "fujitsu,mb86s70-crg11" . Controller+Domain+Port of a clock are now three cells specified by the user node.
* aliases moved into board DTS files
* Voltage supply moved as per-board DT node.
* Removed default overly verbose loglevel=8
* Specify -march=armv7-a flag formcpm.candsmc.Sthat contain ARMv7 specific code.
* Removed wrongly putouter_flush_all(), now using standardv7_exit_coherency_flush()instead of platform specific macro.
* Simplified GPIO offset calculations ingpio-mb86s70.cdriver. And added .remove() for the driver
* ARM MHU driver provided a .remove() to enable module unloading.
* A few other misc cleanups suggested in v1 submission.Thanks.
Jassi Brar (8):
ARM: Add platform support for Fujitsu MB86S7X SoCs
mailbox:arm_mhu: add driver for ARM MHU controller
ARM: MB86S7X: Add MCPM support
clk: Add clock driver for mb86s7x
gpio: Add Fujitsu MB86S7x GPIO driver
dt: mb86s7x: add dt files for MB86S7x evbs
of: add Fujitsu vendor prefix
ARM: MB86S7x: Add configsDocumentation/devicetree/bindings/arm/mb86s7x.txt | 8 + .../bindings/clock/fujitsu,mb86s70-crg11.txt | 26 + .../bindings/gpio/fujitsu,mb86s70-gpio.txt | 20 + .../devicetree/bindings/mailbox/arm-mhu.txt | 33 ++ .../devicetree/bindings/soc/mb86s7x/scb_mhu.txt | 35 ++ .../devicetree/bindings/vendor-prefixes.txt | 1 + MAINTAINERS | 7 + arch/arm/Kconfig | 2 + arch/arm/Makefile | 1 + arch/arm/boot/dts/Makefile | 1 + arch/arm/boot/dts/mb86s70.dtsi | 91 ++++ arch/arm/boot/dts/mb86s70eb.dts | 57 +++ arch/arm/boot/dts/mb86s73.dtsi | 63 +++ arch/arm/boot/dts/mb86s73eb.dts | 44 ++ arch/arm/boot/dts/mb86s7x.dtsi | 140 ++++++ arch/arm/configs/fujitsu_defconfig | 232 +++++++++ arch/arm/configs/multi_v7_defconfig | 5 + arch/arm/mach-mb86s7x/Kconfig | 19 + arch/arm/mach-mb86s7x/Makefile | 3 + arch/arm/mach-mb86s7x/board.c | 23 + arch/arm/mach-mb86s7x/mcpm.c | 318 +++++++++++++ arch/arm/mach-mb86s7x/smc.S | 27 ++ drivers/clk/Makefile | 1 + drivers/clk/clk-mb86s7x.c | 386 +++++++++++++++ drivers/gpio/Kconfig | 6 + drivers/gpio/Makefile | 1 + drivers/gpio/gpio-mb86s7x.c | 232 +++++++++ drivers/mailbox/Kconfig | 7 + drivers/mailbox/Makefile | 2 + drivers/mailbox/arm_mhu.c | 211 ++++++++ drivers/soc/Makefile | 1 + drivers/soc/mb86s7x/Makefile | 4 + drivers/soc/mb86s7x/scb_mhu.c | 528 +++++++++++++++++++++ include/soc/mb86s7x/scb_mhu.h | 105 ++++ 34 files changed, 2640 insertions(+) create mode 100644 Documentation/devicetree/bindings/arm/mb86s7x.txt create mode 100644 Documentation/devicetree/bindings/clock/fujitsu,mb86s70-crg11.txt create mode 100644 Documentation/devicetree/bindings/gpio/fujitsu,mb86s70-gpio.txt create mode 100644 Documentation/devicetree/bindings/mailbox/arm-mhu.txt create mode 100644 Documentation/devicetree/bindings/soc/mb86s7x/scb_mhu.txt create mode 100644 arch/arm/boot/dts/mb86s70.dtsi create mode 100644 arch/arm/boot/dts/mb86s70eb.dts create mode 100644 arch/arm/boot/dts/mb86s73.dtsi create mode 100644 arch/arm/boot/dts/mb86s73eb.dts create mode 100644 arch/arm/boot/dts/mb86s7x.dtsi create mode 100644 arch/arm/configs/fujitsu_defconfig create mode 100644 arch/arm/mach-mb86s7x/Kconfig create mode 100644 arch/arm/mach-mb86s7x/Makefile create mode 100644 arch/arm/mach-mb86s7x/board.c create mode 100644 arch/arm/mach-mb86s7x/mcpm.c create mode 100644 arch/arm/mach-mb86s7x/smc.S create mode 100644 drivers/clk/clk-mb86s7x.c create mode 100644 drivers/gpio/gpio-mb86s7x.c create mode 100644 drivers/mailbox/arm_mhu.c create mode 100644 drivers/soc/mb86s7x/Makefile create mode 100644 drivers/soc/mb86s7x/scb_mhu.c create mode 100644 include/soc/mb86s7x/scb_mhu.h--
1.9.0
Signature · 3 lines
Linaro.org ? Open source software for ARM SoCs | Follow Linaro http://facebook.com/pages/Linaro/155974581091106 - http://twitter.com/#!/linaroorg - http://linaro.org/linaro-blog
Arnd Bergmann
maintainerv4 cover Support for Fujitsu MB86S7X SoCs
Quoted 3 lines · On Monday 02 February 2015 18:51:58 Jassi Brar wrote:
Hi Arnd, Hi Olof,
... just a polite ping on the patchset.
Hi Jassi,
Olof has been handling all the merges so far, but he probably missed this one as it was neither a pull request nor sent to arm at kernel.org.
I've put the arm at kernel.org alias on Cc now, which I assume will make the thread appear in the right folder for him.
Arnd