arm: npcm: add basic support for Nuvoton BMCs
Subsystems (5)
v9 cover arm: npcm: add basic support for Nuvoton BMCs
Addressed comments from:
- Philippe: https://www.spinics.net/lists/arm-kernel/msg621710.html
Summary of changes since previous update:
- Now use SPDX ids instead of traditional license boilerplate. Top of file comments are now C++ style comments.
- Changed reviewers listed in MAINTAINERS.
PATCH v9 1/3 arm: npcm: add basic support for Nuvoton BMCs
Adds basic support for the Nuvoton NPCM750 BMC.
--- arch/arm/Kconfig | 2 ++ arch/arm/Makefile | 1 + arch/arm/mach-npcm/Kconfig | 48 ++++++++++++++++++++++++++ arch/arm/mach-npcm/Makefile | 3 ++ arch/arm/mach-npcm/headsmp.S | 17 ++++++++++ arch/arm/mach-npcm/npcm7xx.c | 20 +++++++++++ arch/arm/mach-npcm/platsmp.c | 81 ++++++++++++++++++++++++++++++++++++++++++++ 7 files changed, 172 insertions(+) create mode 100644 arch/arm/mach-npcm/Kconfig create mode 100644 arch/arm/mach-npcm/Makefile create mode 100644 arch/arm/mach-npcm/headsmp.S create mode 100644 arch/arm/mach-npcm/npcm7xx.c create mode 100644 arch/arm/mach-npcm/platsmp.c
arch/arm/Kconfig +2 -0
@@ -782,6 +782,8 @@ source "arch/arm/mach-netx/Kconfig" source "arch/arm/mach-nomadik/Kconfig" +source "arch/arm/mach-npcm/Kconfig" + source "arch/arm/mach-nspire/Kconfig" source "arch/arm/plat-omap/Kconfig"
arch/arm/Makefile +1 -0
@@ -191,6 +191,7 @@ machine-$(CONFIG_ARCH_MEDIATEK) += mediatek machine-$(CONFIG_ARCH_MXS) += mxs machine-$(CONFIG_ARCH_NETX) += netx machine-$(CONFIG_ARCH_NOMADIK) += nomadik +machine-$(CONFIG_ARCH_NPCM) += npcm machine-$(CONFIG_ARCH_NSPIRE) += nspire machine-$(CONFIG_ARCH_OXNAS) += oxnas machine-$(CONFIG_ARCH_OMAP1) += omap1
arch/arm/mach-npcm/Kconfig new file +48 -0
48 lines not on this page · raw message
arch/arm/mach-npcm/Makefile new file +3 -0
@@ -0,0 +1,3 @@ +AFLAGS_headsmp.o += -march=armv7-a + +obj-$(CONFIG_ARCH_NPCM750) += npcm7xx.o platsmp.o headsmp.o
arch/arm/mach-npcm/headsmp.S new file +17 -0
@@ -0,0 +1,17 @@ +// SPDX-License-Identifier: GPL-2.0 +// Copyright (c) 2018 Nuvoton Technology corporation. +// Copyright 2018 Google, Inc. + +#include <linux/linkage.h> +#include <linux/init.h> +#include <asm/assembler.h> + +/* + * The boot ROM does not start secondary CPUs in SVC mode, so we need to do that + * here. + */ +ENTRY(npcm7xx_secondary_startup) + safe_svcmode_maskall r0 + + b secondary_startup +ENDPROC(npcm7xx_secondary_startup)
arch/arm/mach-npcm/npcm7xx.c new file +20 -0
@@ -0,0 +1,20 @@ +// SPDX-License-Identifier: GPL-2.0 +// Copyright (c) 2018 Nuvoton Technology corporation. +// Copyright 2018 Google, Inc. + +#include <linux/kernel.h> +#include <linux/types.h> +#include <asm/mach/arch.h> +#include <asm/mach-types.h> +#include <asm/mach/map.h> +#include <asm/hardware/cache-l2x0.h> + +static const char *const npcm7xx_dt_match[] = { +"nuvoton,npcm750" , +NULL +}; + +DT_MACHINE_START (NPCM7XX_DT ,"NPCM7XX Chip family" ) + .atag_offset = 0x100, + .dt_compat = npcm7xx_dt_match, +MACHINE_END
arch/arm/mach-npcm/platsmp.c new file +81 -0
81 lines not on this page · raw message
Signature · 1 line
2.16.0.rc1.238.g530d649a79-goog
PATCH v9 2/3 arm: dts: add Nuvoton NPCM750 device tree
In reply to Brendan HigginsAdd a common device tree for all Nuvoton NPCM750 BMCs and a board specific device tree for the NPCM750 (Poleg) evaluation board.
--- .../arm/cpu-enable-method/nuvoton,npcm7xx-smp | 42 ++++++ .../devicetree/bindings/arm/npcm/npcm.txt | 6 + arch/arm/boot/dts/nuvoton-npcm750-evb.dts | 35 +++++ arch/arm/boot/dts/nuvoton-npcm750.dtsi | 162 +++++++++++++++++++++ include/dt-bindings/clock/nuvoton,npcm7xx-clks.h | 35 +++++ 5 files changed, 280 insertions(+) create mode 100644 Documentation/devicetree/bindings/arm/cpu-enable-method/nuvoton,npcm7xx-smp create mode 100644 Documentation/devicetree/bindings/arm/npcm/npcm.txt create mode 100644 arch/arm/boot/dts/nuvoton-npcm750-evb.dts create mode 100644 arch/arm/boot/dts/nuvoton-npcm750.dtsi create mode 100644 include/dt-bindings/clock/nuvoton,npcm7xx-clks.h
Documentation/devicetree/bindings/arm/cpu-enable-method/nuvoton,npcm7xx-smp new file +42 -0
@@ -0,0 +1,42 @@ +========================================================= +Secondary CPU enable-method "nuvoton,npcm7xx-smp" binding +========================================================= + +To apply to all CPUs, a single "nuvoton,npcm7xx-smp" enable method should be +defined in the "cpus" node. + +Enable method name: "nuvoton,npcm7xx-smp" +Compatible machines: "nuvoton,npcm750" +Compatible CPUs: "arm,cortex-a9" +Related properties: (none) + +Note: +This enable method needs valid nodes compatible with "arm,cortex-a9-scu" and +"nuvoton,npcm750-gcr". + +Example: + + cpus { + #address-cells = <1>; + #size-cells = <0>; + enable-method = "nuvoton,npcm7xx-smp"; + + cpu at 0 { + device_type = "cpu"; + compatible = "arm,cortex-a9"; + clocks = <&clk NPCM7XX_CLK_CPU>; + clock-names = "clk_cpu"; + reg = <0>; + next-level-cache = <&L2>; + }; + + cpu at 1 { + device_type = "cpu"; + compatible = "arm,cortex-a9"; + clocks = <&clk NPCM7XX_CLK_CPU>; + clock-names = "clk_cpu"; + reg = <1>; + next-level-cache = <&L2>; + }; + }; +
Documentation/devicetree/bindings/arm/npcm/npcm.txt new file +6 -0
@@ -0,0 +1,6 @@ +NPCM Platforms Device Tree Bindings +----------------------------------- +NPCM750 SoC +Required root node properties: + - compatible = "nuvoton,npcm750"; +
arch/arm/boot/dts/nuvoton-npcm750-evb.dts new file +35 -0
@@ -0,0 +1,35 @@ +// SPDX-License-Identifier: GPL-2.0 +// Copyright (c) 2018 Nuvoton Technology corporation. +// Copyright 2018 Google, Inc. + +/dts-v1/; +#include "nuvoton-npcm750.dtsi" + +/ { + model = "Nuvoton npcm750 Development Board (Device Tree)"; + compatible = "nuvoton,npcm750"; + + chosen { + stdout-path = &serial3; + }; + + memory { + reg = <0 0x40000000>; + }; +}; + +&serial0 { + status = "okay"; +}; + +&serial1 { + status = "okay"; +}; + +&serial2 { + status = "okay"; +}; + +&serial3 { + status = "okay"; +};
arch/arm/boot/dts/nuvoton-npcm750.dtsi new file +162 -0
162 lines not on this page · raw message
include/dt-bindings/clock/nuvoton,npcm7xx-clks.h new file +35 -0
@@ -0,0 +1,35 @@ +// SPDX-License-Identifier: GPL-2.0 +// Copyright (c) 2018 Nuvoton Technology corporation. +// Copyright 2018 Google, Inc. + +#ifndef _DT_BINDINGS_CLK_NPCM7XX_H +#define _DT_BINDINGS_CLK_NPCM7XX_H + +#define NPCM7XX_CLK_PLL0 0 +#define NPCM7XX_CLK_PLL1 1 +#define NPCM7XX_CLK_PLL2 2 +#define NPCM7XX_CLK_GFX 3 +#define NPCM7XX_CLK_APB1 4 +#define NPCM7XX_CLK_APB2 5 +#define NPCM7XX_CLK_APB3 6 +#define NPCM7XX_CLK_APB4 7 +#define NPCM7XX_CLK_APB5 8 +#define NPCM7XX_CLK_MC 9 +#define NPCM7XX_CLK_CPU 10 +#define NPCM7XX_CLK_SPI0 11 +#define NPCM7XX_CLK_SPI3 12 +#define NPCM7XX_CLK_SPIX 13 +#define NPCM7XX_CLK_UART_CORE 14 +#define NPCM7XX_CLK_TIMER 15 +#define NPCM7XX_CLK_HOST_UART 16 +#define NPCM7XX_CLK_MMC 17 +#define NPCM7XX_CLK_SDHC 18 +#define NPCM7XX_CLK_ADC 19 +#define NPCM7XX_CLK_GFX_MEM 20 +#define NPCM7XX_CLK_USB_BRIDGE 21 +#define NPCM7XX_CLK_AXI 22 +#define NPCM7XX_CLK_AHB 23 +#define NPCM7XX_CLK_EMC 24 +#define NPCM7XX_CLK_GMAC 25 + +#endif
Signature · 1 line
2.16.0.rc1.238.g530d649a79-goog
Re: [PATCH v9 2/3] arm: dts: add Nuvoton NPCM750 device tree
Hi Brendan,
Quoted 10 lines · Brendan Higgins
Add a common device tree for all Nuvoton NPCM750 BMCs and a board specific device tree for the NPCM750 (Poleg) evaluation board.
Signed-off-by Brendan Higgins <[email protected]>Reviewed-by Tomer Maimon <[email protected]>Reviewed-by Avi Fishman <[email protected]>Reviewed-by Joel Stanley <[email protected]>Reviewed-by Rob Herring <[email protected]>Tested-by Tomer Maimon <[email protected]>Tested-by Avi Fishman <[email protected]>
This looks well acked, reviewed and tested. How do you plan to have the ARM SoC maintainers merge your patches?
Quoted 4 lines
--- .../arm/cpu-enable-method/nuvoton,npcm7xx-smp | 42 ++++++ .../devicetree/bindings/arm/npcm/npcm.txt | 6 + arch/arm/boot/dts/nuvoton-npcm750-evb.dts | 35 +++++
Quoted 8 lines
arch/arm/boot/dts/nuvoton-npcm750.dtsi | 162 +++++++++++++++++++++ include/dt-bindings/clock/nuvoton,npcm7xx-clks.h | 35 +++++ 5 files changed, 280 insertions(+) create mode 100644 Documentation/devicetree/bindings/arm/cpu-enable-method/nuvoton,npcm7xx-smp create mode 100644 Documentation/devicetree/bindings/arm/npcm/npcm.txt create mode 100644 arch/arm/boot/dts/nuvoton-npcm750-evb.dts create mode 100644 arch/arm/boot/dts/nuvoton-npcm750.dtsi create mode 100644 include/dt-bindings/clock/nuvoton,npcm7xx-clks.h
You need to add nuvoton-npcm750-evb.dts to arch/arm/boot/dts/Makefile
Once you've done that you can add
as I tested this on an EVB.
Quoted 51 lines
arch/arm/boot/dts/nuvoton-npcm750.dtsi new file +45
-0@@ -0,0 +1,162 @@ +// SPDX-License-Identifier: GPL-2.0 +// Copyright (c) 2018 Nuvoton Technology corporation. +// Copyright 2018 Google, Inc. + +#include <dt-bindings/interrupt-controller/arm-gic.h> +#include <dt-bindings/clock/nuvoton,npcm7xx-clks.h> + +/ { + #address-cells = <1>; + #size-cells = <1>; + interrupt-parent = <&gic>; + + cpus { + #address-cells = <1>; + #size-cells = <0>; + enable-method = "nuvoton,npcm7xx-smp"; + + cpu at 0 { + device_type = "cpu"; + compatible = "arm,cortex-a9"; + clocks = <&clk NPCM7XX_CLK_CPU>; + clock-names = "clk_cpu"; + reg = <0>; + next-level-cache = <&l2>; + }; + + cpu at 1 { + device_type = "cpu"; + compatible = "arm,cortex-a9"; + clocks = <&clk NPCM7XX_CLK_CPU>; + clock-names = "clk_cpu"; + reg = <1>; + next-level-cache = <&l2>; + }; + }; + +/* external clock signal rg1refck, supplied by the phy */ +clk-rg1refck { + compatible = "fixed-clock"; + #clock-cells = <0>; + clock-frequency = <125000000>; +}; + +/* external clock signal rg2refck, supplied by the phy */ +clk-rg2refck {
arch/arm/boot/dts/nuvoton-npcm750.dtsi line 55
Quoted 10 lines
arch/arm/boot/dts/nuvoton-npcm750.dtsi new file +10
-0+ compatible = "fixed-clock"; + #clock-cells = <0>; + clock-frequency = <125000000>; +}; + +clk-xin { + compatible = "fixed-clock"; + #clock-cells = <0>; + clock-frequency = <50000000>; +};
The whitespace here needs to be fixed.
Cheers,
Joel
Quoted 8 lines
arch/arm/boot/dts/nuvoton-npcm750.dtsi new file +8
-0+ + soc { + #address-cells = <1>; + #size-cells = <1>; + compatible = "simple-bus"; + interrupt-parent = <&gic>; + ranges = <0x0 0xf0000000 0x00900000>; +
Re: [PATCH v9 2/3] arm: dts: add Nuvoton NPCM750 device tree
Quoted 15 lines · Joel Stanley
Hi Brendan,
Quoted 10 lines · Brendan Higgins
Add a common device tree for all Nuvoton NPCM750 BMCs and a board specific device tree for the NPCM750 (Poleg) evaluation board.
Signed-off-by Brendan Higgins <[email protected]>Reviewed-by Tomer Maimon <[email protected]>Reviewed-by Avi Fishman <[email protected]>Reviewed-by Joel Stanley <[email protected]>Reviewed-by Rob Herring <[email protected]>Tested-by Tomer Maimon <[email protected]>Tested-by Avi Fishman <[email protected]>
Quoted 2 lines
This looks well acked, reviewed and tested. How do you plan to have the ARM SoC maintainers merge your patches?
Following up on an IRC conversation with Brendan:
The process is normally to create a git branch based on on -rc1, apply your patches, and send them to the ARM maintainers. You then push a signed tag to a repository somewhere, send a pull request (a git request-pull email, not a Github PR) and Arnd, Olof or one of the other maintainers will pull your tree some time before the next merge window opens.
Arnd, do we have this documented somewhere for new maintainers to follow?
Cheers,
Joel
Re: [PATCH v9 2/3] arm: dts: add Nuvoton NPCM750 device tree
Quoted 28 lines · Joel Stanley
Quoted 15 lines · Joel Stanley
Hi Brendan,
Quoted 10 lines · Brendan Higgins
Add a common device tree for all Nuvoton NPCM750 BMCs and a board specific device tree for the NPCM750 (Poleg) evaluation board.
Signed-off-by Brendan Higgins <[email protected]>Reviewed-by Tomer Maimon <[email protected]>Reviewed-by Avi Fishman <[email protected]>Reviewed-by Joel Stanley <[email protected]>Reviewed-by Rob Herring <[email protected]>Tested-by Tomer Maimon <[email protected]>Tested-by Avi Fishman <[email protected]>Quoted 2 lines
This looks well acked, reviewed and tested. How do you plan to have the ARM SoC maintainers merge your patches?
Following up on an IRC conversation with Brendan:
The process is normally to create a git branch based on on -rc1, apply your patches, and send them to the ARM maintainers. You then push a signed tag to a repository somewhere, send a pull request (a git request-pull email, not a Github PR) and Arnd, Olof or one of the other maintainers will pull your tree some time before the next merge window opens.
Quoted 2 lines
Arnd, do we have this documented somewhere for new maintainers to follow?
I would add a few things that we had to go through before for Broadcom SoCs:
- send your pull requests to arm at kernel.org and copy Arnd, Olof and Kevin
- you would want to get your PGP key signed by as many people as people as possible which should not be a problem if you are in an area with lots of kernel people like the Bay Area (which reminds me I should do that)
- if you are going to be reasonably active every cycle consider getting a kernel.org account to host your tree (we are still not doing that...)
- for future pull requests, you might want to break them into e.g: DTS, board/Kconfig, drivers, defconfig, maintainers file, and have as little dependencies between each branch to minimize merge conflicts
- build test and run test your changes against at least one other platform, e.g: QEMU to check for multiplatform issues
In case this is of any value, there is a script here that will automatically generate pull requests emails for you based on branches matching what was mentioned above, it will also take care of CC'ing the people involved in the different patches:
https://github.com/ffainelli/misc-scripts/blob/master/gen-pull.pl
It still requires you to create an appropriate tag for the pull requests, though I might semi-automate that in the future, at least spawn an editor and offer some guidance, based on commit messages as to what should be in the pull request email/tag.
HTH
Signature · 1 line
Florian
Re: [PATCH v9 2/3] arm: dts: add Nuvoton NPCM750 device tree
<snip>
Quoted 17 lines
Quoted 2 lines
Arnd, do we have this documented somewhere for new maintainers to follow?
I would add a few things that we had to go through before for Broadcom SoCs:
- send your pull requests to arm at kernel.org and copy Arnd, Olof and Kevin
- you would want to get your PGP key signed by as many people as people as possible which should not be a problem if you are in an area with lots of kernel people like the Bay Area (which reminds me I should do that)
- if you are going to be reasonably active every cycle consider getting a kernel.org account to host your tree (we are still not doing that...)
- for future pull requests, you might want to break them into e.g: DTS, board/Kconfig, drivers, defconfig, maintainers file, and have as little dependencies between each branch to minimize merge conflicts
- build test and run test your changes against at least one other platform, e.g: QEMU to check for multiplatform issues
In case this is of any value, there is a script here that will automatically generate pull requests emails for you based on branches matching what was mentioned above, it will also take care of CC'ing the people involved in the different patches:
Quoted 8 lines
https://github.com/ffainelli/misc-scripts/blob/master/gen-pull.pl
It still requires you to create an appropriate tag for the pull requests, though I might semi-automate that in the future, at least spawn an editor and offer some guidance, based on commit messages as to what should be in the pull request email/tag.
HTH
--
Florian
Thanks Florian, this was extremely helpful!
Re: [PATCH v9 2/3] arm: dts: add Nuvoton NPCM750 device tree
In reply to Brendan HigginsQuoted 10 lines · Brendan Higgins
Add a common device tree for all Nuvoton NPCM750 BMCs and a board specific device tree for the NPCM750 (Poleg) evaluation board.
Signed-off-by Brendan Higgins <[email protected]>Reviewed-by Tomer Maimon <[email protected]>Reviewed-by Avi Fishman <[email protected]>Reviewed-by Joel Stanley <[email protected]>Reviewed-by Rob Herring <[email protected]>Tested-by Tomer Maimon <[email protected]>Tested-by Avi Fishman <[email protected]>
...
Quoted 1 line
+ enable-method = "nuvoton,npcm7xx-smp";
I see this has already been reviewed quite a bit, but I'm curious about the 'npcm7xx'
part here. Shouldn't that be a real chip name rather than a wildcard?
Arnd
Avi Fishman
maintainerRe: [PATCH v9 2/3] arm: dts: add Nuvoton NPCM750 device tree
Quoted 12 lines · Arnd Bergmann
Quoted 10 lines · Brendan Higgins
Add a common device tree for all Nuvoton NPCM750 BMCs and a board specific device tree for the NPCM750 (Poleg) evaluation board.
Signed-off-by Brendan Higgins <[email protected]>Reviewed-by Tomer Maimon <[email protected]>Reviewed-by Avi Fishman <[email protected]>Reviewed-by Joel Stanley <[email protected]>Reviewed-by Rob Herring <[email protected]>Tested-by Tomer Maimon <[email protected]>Tested-by Avi Fishman <[email protected]>
Quoted 8 lines
...
Quoted 1 line
+ enable-method = "nuvoton,npcm7xx-smp";
I see this has already been reviewed quite a bit, but I'm curious about the 'npcm7xx'
part here. Shouldn't that be a real chip name rather than a wildcard?Arnd
There is a family of npcm7xx, some with SMP and some without. For those who has it, it is common for all to use the same "nuvoton,npcm7xx-smp".
Avi
Re: [PATCH v9 2/3] arm: dts: add Nuvoton NPCM750 device tree
Quoted 20 lines · Avi Fishman
Quoted 19 lines · Arnd Bergmann
Quoted 10 lines · Brendan Higgins
Add a common device tree for all Nuvoton NPCM750 BMCs and a board specific device tree for the NPCM750 (Poleg) evaluation board.
Signed-off-by Brendan Higgins <[email protected]>Reviewed-by Tomer Maimon <[email protected]>Reviewed-by Avi Fishman <[email protected]>Reviewed-by Joel Stanley <[email protected]>Reviewed-by Rob Herring <[email protected]>Tested-by Tomer Maimon <[email protected]>Tested-by Avi Fishman <[email protected]>...
Quoted 1 line
+ enable-method = "nuvoton,npcm7xx-smp";
I see this has already been reviewed quite a bit, but I'm curious about the 'npcm7xx'
part here. Shouldn't that be a real chip name rather than a wildcard?
Quoted 5 lines
Quoted 1 line
Arnd
There is a family of npcm7xx, some with SMP and some without. For those who has it, it is common for all to use the same "nuvoton,npcm7xx-smp".
I think Arnd is right. In this case it should be "nuvoton,npcm750-smp". We can use CPU_METHOD_OF_DECLARE to alias to as many compatible properties as needed.
Although everything in the 7xx family currently is either single core or has the same SMP behavior, you could paint yourself into a corner if you were to make one SMP device in the 7xx family which behaves differently from all other devices and then need to come up with new compatible string names just for that.
Quoted 2 lines
Avi
Re: [PATCH v9 2/3] arm: dts: add Nuvoton NPCM750 device tree
Quoted 25 lines · Brendan Higgins
Quoted 16 lines · Avi Fishman
Quoted 15 lines · Arnd Bergmann
Quoted 10 lines · Brendan Higgins
Add a common device tree for all Nuvoton NPCM750 BMCs and a board specific device tree for the NPCM750 (Poleg) evaluation board.
Signed-off-by Brendan Higgins <[email protected]>Reviewed-by Tomer Maimon <[email protected]>Reviewed-by Avi Fishman <[email protected]>Reviewed-by Joel Stanley <[email protected]>Reviewed-by Rob Herring <[email protected]>Tested-by Tomer Maimon <[email protected]>Tested-by Avi Fishman <[email protected]>...
Quoted 1 line
+ enable-method = "nuvoton,npcm7xx-smp";
Quoted 7 lines
Quoted 3 lines
I see this has already been reviewed quite a bit, but I'm curious about the 'npcm7xx'
part here. Shouldn't that be a real chip name rather than a wildcard?There is a family of npcm7xx, some with SMP and some without. For those who has it, it is common for all to use the same "nuvoton,npcm7xx-smp".
Quoted 7 lines
I think Arnd is right. In this case it should be "nuvoton,npcm750-smp". We can use
CPU_METHOD_OF_DECLAREto alias to as many compatible properties as needed.Although everything in the 7xx family currently is either single core or has the same SMP behavior, you could paint yourself into a corner if you were to make one SMP device in the 7xx family which behaves differently from all other devices and then need to come up with new compatible string names just for that.
Right, this is the reason for the very simple 'no wildcards in DT identifiers' rule.
There simply isn't a reason to make an exception here.
Arnd
PATCH v9 3/3 MAINTAINERS: Add entry for the Nuvoton NPCM architecture
In reply to Brendan HigginsAdd maintainers and reviewers for the Nuvoton NPCM architecture.
--- MAINTAINERS | 14 ++++++++++++++ 1 file changed, 14 insertions(+)
MAINTAINERS +14 -0
@@ -1598,6 +1598,20 @@ F: drivers/pinctrl/nomadik/ F: drivers/i2c/busses/i2c-nomadik.c T: git git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-nomadik.git +ARM/NUVOTON NPCM ARCHITECTURE +M: Avi Fishman <[email protected]> +M: Tomer Maimon <[email protected]> +R: Patrick Venture <[email protected]> +R: Nancy Yuen <[email protected]> +R: Brendan Higgins <[email protected]> +L: openbmc at lists.ozlabs.org (moderated for non-subscribers) +S: Supported +F: arch/arm/mach-npcm/ +F: arch/arm/boot/dts/nuvoton-npcm* +F: include/dt-bindings/clock/nuvoton,npcm7xx-clks.h +F: drivers/*/*npcm* +F: Documentation/*/*npcm* + ARM/NUVOTON W90X900 ARM ARCHITECTURE M: Wan ZongShun <[email protected]> L: linux-arm-kernel at lists.infradead.org (moderated for non-subscribers)
Signature · 1 line
2.16.0.rc1.238.g530d649a79-goog