lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 22 Oct 2013 17:27:11 +0200 From: Heiko Stübner <heiko@...ech.de> To: "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org> Cc: arm@...nel.org, Grant Likely <grant.likely@...aro.org>, Rob Herring <robherring2@...il.com>, devicetree@...r.kernel.org, Russell King <linux@....linux.org.uk>, Philipp Zabel <p.zabel@...gutronix.de>, linux-kernel@...r.kernel.org, "Greg Kroah-Hartman" <gregkh@...uxfoundation.org>, Ulrich Prinz <ulrich.prinz@...glemail.com>, Matt Sealey <neko@...uhatsu.net>, Fabio Estevam <festevam@...il.com> Subject: [PATCH RESEND v5 3/5] ARM: rockchip: add sram dt nodes and documentation The Rockchip SoCs need a special part of their sram for bringup of additional cores. Therefore also limit the public area when adding the mmio-sram node to keep the sram driver from using this space. Signed-off-by: Heiko Stuebner <heiko@...ech.de> Tested-by: Ulrich Prinz <ulrich.prinz@...glemail.com> --- .../devicetree/bindings/arm/rockchip/smp-sram.txt | 24 ++++++++++++++++++++ arch/arm/boot/dts/rk3066a.dtsi | 6 +++++ arch/arm/boot/dts/rk3188.dtsi | 6 +++++ 3 files changed, 36 insertions(+) create mode 100644 Documentation/devicetree/bindings/arm/rockchip/smp-sram.txt diff --git a/Documentation/devicetree/bindings/arm/rockchip/smp-sram.txt b/Documentation/devicetree/bindings/arm/rockchip/smp-sram.txt new file mode 100644 index 0000000..0c88d06 --- /dev/null +++ b/Documentation/devicetree/bindings/arm/rockchip/smp-sram.txt @@ -0,0 +1,24 @@ +Rockchip SRAM for smp bringup: +------------------------------ + +Rockchip's smp-capable SoCs use the first part of the sram for the bringup +of the cores. Once the core gets powered up it executes the code that is +residing at the very beginning of the sram. + +Therefore the available space has to be limited to exclude this area using +the available property of the sram node. + +Required node properties: +- compatible : should contain both "rockchip,rk3066-sram", "mmio-sram" + so that the smp code can select the correct sram node. + +The rest of the properties should follow the generic mmio-sram discription +found in ../../misc/sram.txt + +Example: + + sram: sram@...80000 { + compatible = "rockchip,rk3066-sram", "mmio-sram"; + reg = <0x10080000 0x10000>; + available = <0x50 0xffb0>; + }; diff --git a/arch/arm/boot/dts/rk3066a.dtsi b/arch/arm/boot/dts/rk3066a.dtsi index 2218c64..e91048b 100644 --- a/arch/arm/boot/dts/rk3066a.dtsi +++ b/arch/arm/boot/dts/rk3066a.dtsi @@ -64,6 +64,12 @@ clock-names = "timer", "pclk"; }; + sram: sram@...80000 { + compatible = "rockchip,rk3066-sram", "mmio-sram"; + reg = <0x10080000 0x10000>; + available = <0x50 0xffb0>; + }; + pinctrl@...08000 { compatible = "rockchip,rk3066a-pinctrl"; reg = <0x20008000 0x150>; diff --git a/arch/arm/boot/dts/rk3188.dtsi b/arch/arm/boot/dts/rk3188.dtsi index 1a26b03..a9885df 100644 --- a/arch/arm/boot/dts/rk3188.dtsi +++ b/arch/arm/boot/dts/rk3188.dtsi @@ -60,6 +60,12 @@ interrupts = <GIC_PPI 13 0xf04>; }; + sram: sram@...80000 { + compatible = "rockchip,rk3066-sram", "mmio-sram"; + reg = <0x10080000 0x8000>; + available = <0x50 0x7fb0>; + }; + pinctrl@...08000 { compatible = "rockchip,rk3188-pinctrl"; reg = <0x20008000 0xa0>, -- 1.7.10.4 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists