From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [RFC 1/3] ARM: shmobile: rcar-gen2: Add generic "renesas,rcar-gen2" machine
Date: Mon, 25 May 2015 01:17:10 +0000 [thread overview]
Message-ID: <20150525011710.GH24690@verge.net.au> (raw)
In-Reply-To: <1432205413-9584-2-git-send-email-ulrich.hecht+renesas@gmail.com>
Hi Ulrich,
On Thu, May 21, 2015 at 12:50:11PM +0200, Ulrich Hecht wrote:
> This will do for all Gen2 SoCs that do not need SoC-specific setup.
From my point of view the qualification above implies there is
a problem with this approach.
>
> Signed-off-by: Ulrich Hecht <ulrich.hecht+renesas@gmail.com>
> ---
> Documentation/devicetree/bindings/arm/shmobile.txt | 8 ++++++--
> arch/arm/mach-shmobile/setup-rcar-gen2.c | 13 +++++++++++++
> 2 files changed, 19 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/arm/shmobile.txt b/Documentation/devicetree/bindings/arm/shmobile.txt
> index c4f19b2..29886ab 100644
> --- a/Documentation/devicetree/bindings/arm/shmobile.txt
> +++ b/Documentation/devicetree/bindings/arm/shmobile.txt
> @@ -27,12 +27,16 @@ SoCs:
> compatible = "renesas,r8a7793"
> - R-Car E2 (R8A77940)
> compatible = "renesas,r8a7794"
> + - R-Car Gen2 (Generic R-Car Generation 2 SoC)
> + This applies to Generation 2 R-Car SoCs that do not require SoC-specific
> + setup code.
> + compatible = "renesas,rcar-gen2"
>
>
> Boards:
>
> - Alt
> - compatible = "renesas,alt", "renesas,r8a7794"
> + compatible = "renesas,alt", "renesas,r8a7794", "renesas,rcar-gen2"
> - APE6-EVM
> compatible = "renesas,ape6evm", "renesas,r8a73a4"
> - Atmark Techno Armadillo-800 EVA
> @@ -44,7 +48,7 @@ Boards:
> - Genmai (RTK772100BC00000BR)
> compatible = "renesas,genmai", "renesas,r7s72100"
> - Gose
> - compatible = "renesas,gose", "renesas,r8a7793"
> + compatible = "renesas,gose", "renesas,r8a7793", "renesas,rcar-gen2"
> - Henninger
> compatible = "renesas,henninger", "renesas,r8a7791"
> - Koelsch (RTP0RC7791SEB00010S)
> diff --git a/arch/arm/mach-shmobile/setup-rcar-gen2.c b/arch/arm/mach-shmobile/setup-rcar-gen2.c
> index 5d13595..0f6b48b 100644
> --- a/arch/arm/mach-shmobile/setup-rcar-gen2.c
> +++ b/arch/arm/mach-shmobile/setup-rcar-gen2.c
> @@ -201,3 +201,16 @@ void __init rcar_gen2_reserve(void)
> &rcar_gen2_dma_contiguous, true);
> #endif
> }
> +
> +static const char *rcar_gen2_boards_compat_dt[] __initconst = {
> + "renesas,rcar-gen2",
> + NULL,
> +};
I would rather not have renesas,rcar-gen2 above and rather have
each SoC that this covers listed above.
> +
> +DT_MACHINE_START(RCAR_GEN2_DT, "Generic R-Car Gen2 (Flattened Device Tree)")
> + .init_early = shmobile_init_delay,
> + .init_time = rcar_gen2_timer_init,
> + .init_late = shmobile_init_late,
> + .reserve = rcar_gen2_reserve,
> + .dt_compat = rcar_gen2_boards_compat_dt,
> +MACHINE_END
> --
> 2.3.5
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-sh" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2015-05-25 1:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 10:50 [RFC 1/3] ARM: shmobile: rcar-gen2: Add generic "renesas,rcar-gen2" machine Ulrich Hecht
2015-05-23 18:02 ` Laurent Pinchart
2015-05-25 1:17 ` Simon Horman [this message]
2015-05-26 8:01 ` Geert Uytterhoeven
2015-05-26 8:04 ` Geert Uytterhoeven
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=20150525011710.GH24690@verge.net.au \
--to=horms@verge.net.au \
--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