From: t.figa@samsung.com (Tomasz Figa)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 07/10] ARM: dts: Add initial device tree support for Exynos5420
Date: Mon, 17 Jun 2013 13:44:17 +0200 [thread overview]
Message-ID: <3228621.2EHTYISgy0@amdc1227> (raw)
In-Reply-To: <1371466836-4111-8-git-send-email-chander.kashyap@linaro.org>
--
Tomasz Figa
Linux Kernel Developer
Samsung R&D Institute Poland
Samsung Electronics
On Monday 17 of June 2013 16:30:32 Chander Kashyap wrote:
> Add initial device tree nodes for Exynos5420 SoC and SMDK5420 board.
>
> Signed-off-by: Chander Kashyap <chander.kashyap@linaro.org>
> ---
> arch/arm/boot/dts/Makefile | 1 +
> arch/arm/boot/dts/exynos5420-smdk5420.dts | 33 +++++++++
> arch/arm/boot/dts/exynos5420.dtsi | 103
> +++++++++++++++++++++++++++++ 3 files changed, 137 insertions(+)
> create mode 100644 arch/arm/boot/dts/exynos5420-smdk5420.dts
> create mode 100644 arch/arm/boot/dts/exynos5420.dtsi
>
> diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
> index f0895c5..5efa7e0 100644
> --- a/arch/arm/boot/dts/Makefile
> +++ b/arch/arm/boot/dts/Makefile
> @@ -57,6 +57,7 @@ dtb-$(CONFIG_ARCH_EXYNOS) += exynos4210-origen.dtb \
> exynos5440-sd5v1.dtb \
> exynos5250-smdk5250.dtb \
> exynos5250-snow.dtb \
> + exynos5420-smdk5420.dtb \
> exynos5440-ssdk5440.dtb
> dtb-$(CONFIG_ARCH_HIGHBANK) += highbank.dtb \
> ecx-2000.dtb
> diff --git a/arch/arm/boot/dts/exynos5420-smdk5420.dts
> b/arch/arm/boot/dts/exynos5420-smdk5420.dts new file mode 100644
> index 0000000..d14ece5
> --- /dev/null
> +++ b/arch/arm/boot/dts/exynos5420-smdk5420.dts
> @@ -0,0 +1,33 @@
> +/*
> + * SAMSUNG SMDK5420 board device tree source
> + *
> + * Copyright (c) 2013 Samsung Electronics Co., Ltd.
> + * http://www.samsung.com
> + *
> + * 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.
> +*/
> +
> +/dts-v1/;
> +#include "exynos5420.dtsi"
> +
> +/ {
> + model = "Samsung SMDK5420 board based on EXYNOS5420";
> + compatible = "samsung,smdk5420", "samsung,exynos5420";
> +
> + memory {
> + reg = <0x20000000 0x80000000>;
> + };
> +
> + chosen {
> + bootargs = "console=ttySAC2,115200 init=/linuxrc";
> + };
> +
> + fixed-rate-clocks {
> + oscclk {
> + compatible = "samsung,exynos5420-oscclk";
> + clock-frequency = <24000000>;
> + };
> + };
> +};
> diff --git a/arch/arm/boot/dts/exynos5420.dtsi
> b/arch/arm/boot/dts/exynos5420.dtsi new file mode 100644
> index 0000000..e865be5
> --- /dev/null
> +++ b/arch/arm/boot/dts/exynos5420.dtsi
> @@ -0,0 +1,103 @@
> +/*
> + * SAMSUNG EXYNOS5420 SoC device tree source
> + *
> + * Copyright (c) 2013 Samsung Electronics Co., Ltd.
> + * http://www.samsung.com
> + *
> + * SAMSUNG EXYNOS54200 SoC device nodes are listed in this file.
> + * EXYNOS5420 based board files can include this file and provide
> + * values for board specfic bindings.
> + *
> + * 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 "exynos5.dtsi"
> +/ {
> + compatible = "samsung,exynos5420";
> +
> + cpus {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + cpu0: cpu at 0 {
> + device_type = "cpu";
> + compatible = "arm,cortex-a15";
> + reg = <0x0>;
> + clock-frequency = <800000000>;
It is the only frequency at which this SoC can run? What code does actually
use this property? Can't this frequency be read by calling clk_get_rate() on
armclk?
Otherwise looks good:
Reviewed-by: Tomasz Figa <t.figa@samsung.com>
Best regards,
Tomasz
> + };
> +
> + cpu1: cpu at 1 {
> + device_type = "cpu";
> + compatible = "arm,cortex-a15";
> + reg = <0x1>;
> + clock-frequency = <800000000>;
> + };
> +
> + cpu2: cpu at 2 {
> + device_type = "cpu";
> + compatible = "arm,cortex-a15";
> + reg = <0x2>;
> + clock-frequency = <800000000>;
> + };
> +
> + cpu3: cpu at 3 {
> + device_type = "cpu";
> + compatible = "arm,cortex-a15";
> + reg = <0x3>;
> + clock-frequency = <800000000>;
> + };
> + };
> +
> + clock: clock-controller at 0x10010000 {
> + compatible = "samsung,exynos5420-clock";
> + reg = <0x10010000 0x30000>;
> + #clock-cells = <1>;
> + };
> +
> + mct at 101C0000 {
> + compatible = "samsung,exynos4210-mct";
> + reg = <0x101C0000 0x800>;
> + interrupt-controller;
> + #interrups-cells = <1>;
> + interrupt-parent = <&mct_map>;
> + interrupts = <0>, <1>, <2>, <3>, <4>, <5>, <6>, <7>;
> + clocks = <&clock 1>, <&clock 315>;
> + clock-names = "fin_pll", "mct";
> +
> + mct_map: mct-map {
> + #interrupt-cells = <1>;
> + #address-cells = <0>;
> + #size-cells = <0>;
> + interrupt-map = <0 &combiner 23 3>,
> + <1 &combiner 23 4>,
> + <2 &combiner 25 2>,
> + <3 &combiner 25 3>,
> + <4 &gic 0 120 0>,
> + <5 &gic 0 121 0>,
> + <6 &gic 0 122 0>,
> + <7 &gic 0 123 0>;
> + };
> + };
> +
> + serial at 12C00000 {
> + clocks = <&clock 257>, <&clock 128>;
> + clock-names = "uart", "clk_uart_baud0";
> + };
> +
> + serial at 12C10000 {
> + clocks = <&clock 258>, <&clock 129>;
> + clock-names = "uart", "clk_uart_baud0";
> + };
> +
> + serial at 12C20000 {
> + clocks = <&clock 259>, <&clock 130>;
> + clock-names = "uart", "clk_uart_baud0";
> + };
> +
> + serial at 12C30000 {
> + clocks = <&clock 260>, <&clock 131>;
> + clock-names = "uart", "clk_uart_baud0";
> + };
> +};
next prev parent reply other threads:[~2013-06-17 11:44 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 11:00 [PATCH v3 00/10] ARM: Exynos: Add Exynos5420 SoC support Chander Kashyap
2013-06-17 11:00 ` [PATCH v3 01/10] ARM: dts: fork out common Exynos5 nodes Chander Kashyap
2013-06-17 11:38 ` Kukjin Kim
2013-06-18 4:24 ` Chander Kashyap
2013-06-17 11:00 ` [PATCH v3 02/10] ARM: dts: list the CPU nodes for Exynos5250 Chander Kashyap
2013-06-17 11:00 ` [PATCH v3 03/10] ARM: Exynos: Add support for Exynos5420 SoC Chander Kashyap
2013-06-17 11:00 ` [PATCH v3 04/10] serial: samsung: select Exynos specific driver data if ARCH_EXYNOS is defined Chander Kashyap
2013-06-17 11:45 ` Kukjin Kim
2013-06-18 10:31 ` Kukjin Kim
2013-06-18 15:19 ` 'Greg Kroah-Hartman'
2013-06-17 11:00 ` [PATCH v3 05/10] ARM: Exynos: use four additional chipid bits to identify Exynos family Chander Kashyap
2013-06-17 11:00 ` [PATCH v3 06/10] clk: exynos5420: register clocks using common clock framework Chander Kashyap
2013-06-17 11:49 ` Kukjin Kim
2013-06-17 12:27 ` Arnd Bergmann
2013-06-18 4:09 ` Chander Kashyap
2013-06-18 14:01 ` Arnd Bergmann
2013-06-18 14:26 ` Tomasz Figa
2013-06-18 17:13 ` Arnd Bergmann
2013-06-17 11:00 ` [PATCH v3 07/10] ARM: dts: Add initial device tree support for Exynos5420 Chander Kashyap
2013-06-17 11:44 ` Tomasz Figa [this message]
2013-06-18 4:21 ` Chander Kashyap
2013-06-18 7:36 ` Tomasz Figa
2013-06-17 11:00 ` [PATCH v3 08/10] clocksource: exynos_mct: use (request/free)_irq calls for local timer registration Chander Kashyap
2013-06-17 11:53 ` Kukjin Kim
2013-06-18 4:11 ` Chander Kashyap
2013-06-17 11:00 ` [PATCH v3 09/10] ARM: Exynos: add secondary CPU boot base location for Exynos5420 Chander Kashyap
2013-06-17 11:00 ` [PATCH v3 10/10] ARM: Exynos: extend soft-reset support " Chander Kashyap
2013-06-17 12:21 ` Arnd Bergmann
2013-06-18 4:10 ` Chander Kashyap
2013-06-17 11:45 ` [PATCH v3 00/10] ARM: Exynos: Add Exynos5420 SoC support Tomasz Figa
2013-06-17 11:56 ` Kukjin Kim
2013-06-18 4:28 ` Chander Kashyap
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=3228621.2EHTYISgy0@amdc1227 \
--to=t.figa@samsung.com \
--cc=linux-arm-kernel@lists.infradead.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