From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 3/4 v3][RFC] arm64: renesas: Add initial r8a7795 SoC support
Date: Tue, 04 Aug 2015 12:22:14 +0000 [thread overview]
Message-ID: <1559394.i3FG4v33fI@avalon> (raw)
In-Reply-To: <873801w377.wl%kuninori.morimoto.gx@renesas.com>
Hi Morimoto-san,
Thank you for the patch.
On Monday 03 August 2015 01:53:23 Kuninori Morimoto wrote:
> From: Gaku Inami <gaku.inami.xw@bp.renesas.com>
>
> Signed-off-by: Gaku Inami <gaku.inami.xw@bp.renesas.com>
> Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
> ---
> v2 -> v3
>
> - no change
>
> Documentation/devicetree/bindings/arm/shmobile.txt | 2 +
> .../bindings/clock/renesas,cpg-mstp-clocks.txt | 1 +
> arch/arm64/boot/dts/Makefile | 1 +
> arch/arm64/boot/dts/renesas/Makefile | 5 ++
> arch/arm64/boot/dts/renesas/r8a7795.dtsi | 93 +++++++++++++++++++
> include/dt-bindings/clock/r8a7795-clock.h | 31 ++++++++
> 6 files changed, 133 insertions(+)
> create mode 100644 arch/arm64/boot/dts/renesas/Makefile
> create mode 100644 arch/arm64/boot/dts/renesas/r8a7795.dtsi
> create mode 100644 include/dt-bindings/clock/r8a7795-clock.h
[snip]
> diff --git a/arch/arm64/boot/dts/renesas/r8a7795.dtsi
> b/arch/arm64/boot/dts/renesas/r8a7795.dtsi new file mode 100644
> index 0000000..0f298c3
> --- /dev/null
> +++ b/arch/arm64/boot/dts/renesas/r8a7795.dtsi
> @@ -0,0 +1,93 @@
> +/*
> + * Device Tree Source for the r8a7795 SoC
> + *
> + * Copyright (C) 2015 Renesas Electronics Corp.
> + *
> + * This file is licensed under the terms of the GNU General Public License
> + * version 2. This program is licensed "as is" without any warranty of any
> + * kind, whether express or implied.
> + */
> +
> +#include <dt-bindings/clock/r8a7795-clock.h>
> +#include <dt-bindings/interrupt-controller/arm-gic.h>
> +
> +/ {
> + compatible = "renesas,r8a7795";
> + interrupt-parent = <&gic>;
> + #address-cells = <2>;
> + #size-cells = <2>;
> +
> + cpus {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + /* 1core only at this point */
> + a57_0: cpu@0 {
> + compatible = "arm,cortex-a57", "arm,armv8";
> + reg = <0x0>;
> + device_type = "cpu";
> + };
> + };
> +
> + gic: interrupt-controller@0xf1010000 {
> + compatible = "arm,gic-400";
> + #interrupt-cells = <3>;
> + #address-cells = <0>;
> + interrupt-controller;
> + reg = <0x0 0xf1010000 0 0x1000>,
> + <0x0 0xf1020000 0 0x2000>;
> + interrupts = <GIC_PPI 9
> + (GIC_CPU_MASK_SIMPLE(1) | IRQ_TYPE_LEVEL_HIGH)>;
> + };
Shouldn't the memory-mapped peripherals be put under a bus node instead of the
root DT node ?
> + timer {
> + compatible = "arm,armv8-timer";
> + interrupts = <GIC_PPI 13
> + (GIC_CPU_MASK_SIMPLE(1) | IRQ_TYPE_LEVEL_LOW)>,
> + <GIC_PPI 14
> + (GIC_CPU_MASK_SIMPLE(1) | IRQ_TYPE_LEVEL_LOW)>,
> + <GIC_PPI 11
> + (GIC_CPU_MASK_SIMPLE(1) | IRQ_TYPE_LEVEL_LOW)>,
> + <GIC_PPI 10
> + (GIC_CPU_MASK_SIMPLE(1) | IRQ_TYPE_LEVEL_LOW)>;
> + };
> +
> + clocks {
Let's try to make it right from the start on Gen3. The CPG node should be a
direct child of the bus node mentioned above, and the MSTP clocks should be
children of the CPG node.
I'm not sure where to put the non-memory-mapped clocks though, should they be
directly under the root node ? It would make sense for extal_clk, but how
about the fixed-factor clocks ? Should they be children of the CPG node too ?
> + #address-cells = <2>;
> + #size-cells = <2>;
> + ranges;
> +
> + extal_clk: extal_clk {
> + compatible = "fixed-clock";
> + #clock-cells = <0>;
> + clock-frequency = <0>;
> + clock-output-names = "extal";
> + };
> + cpg_clocks: cpg_clocks@e6150000 {
> + compatible = "renesas,r8a7795-cpg-clocks",
> + "renesas,rcar-gen3-cpg-clocks";
> + reg = <0 0xe6150000 0 0x1000>;
> + clocks = <&extal_clk>;
> + #clock-cells = <1>;
> + clock-output-names = "main", "pll0", "pll1","pll2",
> + "pll3", "pll4";
> + };
> + p_clk: p_clk {
> + compatible = "fixed-factor-clock";
> + clocks = <&cpg_clocks RCAR_GEN3_CLK_PLL1>;
> + #clock-cells = <0>;
> + clock-div = <24>;
> + clock-mult = <1>;
> + clock-output-names = "p";
> + };
> + mstp3_clks: mstp3_clks@e615013c {
> + compatible = "renesas,r8a7795-mstp-clocks",
> + "renesas,cpg-mstp-clocks";
> + reg = <0 0xe615013c 0 4>, <0 0xe6150048 0 4>;
> + clocks = <&p_clk>;
> + #clock-cells = <1>;
> + renesas,clock-indices = <RCAR_GEN3_CLK_IRDA>;
> + clock-output-names = "irda";
> + };
> + };
> +};
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2015-08-04 12:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-03 1:51 [PATCH 0/4 v3][RFC] arm64: Renesas Gen3 initial patch Kuninori Morimoto
2015-08-03 1:53 ` [PATCH 3/4 v3][RFC] arm64: renesas: Add initial r8a7795 SoC support Kuninori Morimoto
2015-08-04 8:15 ` Kuninori Morimoto
2015-08-04 12:22 ` Laurent Pinchart [this message]
2015-08-04 12:34 ` Geert Uytterhoeven
2015-08-18 0:20 ` Michael Turquette
2015-08-19 7:49 ` Geert Uytterhoeven
2015-08-19 21:29 ` Laurent Pinchart
2015-08-20 7:43 ` Geert Uytterhoeven
2015-08-20 19:48 ` Laurent Pinchart
2015-08-24 7:51 ` Geert Uytterhoeven
2015-08-28 8:44 ` Geert Uytterhoeven
2015-08-03 2:44 ` [PATCH 0/4 v3][RFC] arm64: Renesas Gen3 initial patch Simon Horman
2015-08-03 6:59 ` Simon Horman
2015-08-03 8:29 ` Kuninori Morimoto
2015-08-03 16:56 ` Geert Uytterhoeven
2015-08-04 0:52 ` Simon Horman
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=1559394.i3FG4v33fI@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-sh@vger.kernel.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