devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Vladimir Barinov <vladimir.barinov@cogentembedded.com>
Cc: Simon Horman <horms@verge.net.au>,
	Magnus Damm <magnus.damm@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will.deacon@arm.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
	Pantelis Antoniou <pantelis.antoniou@konsulko.com>
Subject: Re: [PATCH v2 04/18] arm64: dts: m3ulcb-kf: initial device tree
Date: Wed, 20 Sep 2017 14:32:28 +0200	[thread overview]
Message-ID: <CAMuHMdX-7MG2fCzJ-K5iQLnJcmZBaWjqMhmOhCxEemmWTh9pvw@mail.gmail.com> (raw)
In-Reply-To: <1505398732-4614-1-git-send-email-vladimir.barinov@cogentembedded.com>

Hi Vladimir,

[CC Pantelis]

On Thu, Sep 14, 2017 at 4:18 PM, Vladimir Barinov
<vladimir.barinov@cogentembedded.com> wrote:
> Add the initial device tree for the M3ULCB with Kingfisher extension
> infotainment board.
>
> Signed-off-by: Vladimir Barinov <vladimir.barinov@cogentembedded.com>
> ---
> Changes in version 2:
> - added own compatible value "shimafuji,kingfisher"

Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>

Some food for thought below...

> --- /dev/null
> +++ b/arch/arm64/boot/dts/renesas/r8a7796-m3ulcb-kf.dts
> @@ -0,0 +1,19 @@
> +/*
> + * Device Tree Source for the M3ULCB Kingfisher board
> + *
> + * Copyright (C) 2017 Renesas Electronics Corp.
> + * Copyright (C) 2017 Cogent Embedded, Inc.
> + *
> + * 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 "r8a7796-m3ulcb.dts"

Ideally, we don't include *.dts files, only *.dtsi.
But I don't see a better immediate solution.

> +#include "ulcb-kf.dtsi"

As the Kingfisher is actually an expansion board for H3ULCB (with R-Car H3
ES1.1 and ES2.0) and M3ULCB (with R-Car M3-W), turning ulcb-kf.dtsi into a
DT overlay would make sense.
That would also solve the issue of the 3 extra DTSes needed for all possible
combinations of ULCB and Kingfisher (r8a7795-es1-h3ulcb-kf.dts,
r8a7795-h3ulcb-kf.dts, r8a7796-h3ulcb-kf.dts (perhaps more to follow?)).

But that's too premature, without upstream support for the easy loading of
DT overlays.

> +/ {
> +       model = "Renesas M3ULCB Kingfisher board based on r8a7796";
> +       compatible = "shimafuji,kingfisher", "renesas,m3ulcb",
> +                    "renesas,r8a7796";
> +};

And how to support from an overlay the addition of "shimafuji,kingfisher" to
(not replacement of!) the main compatible value?

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  reply	other threads:[~2017-09-20 12:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-14 14:18 [PATCH v2 04/18] arm64: dts: m3ulcb-kf: initial device tree Vladimir Barinov
2017-09-20 12:32 ` Geert Uytterhoeven [this message]
     [not found]   ` <CAMuHMdX-7MG2fCzJ-K5iQLnJcmZBaWjqMhmOhCxEemmWTh9pvw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-09-21  8:20     ` Simon Horman
2017-09-21  8:24       ` Simon Horman
2017-09-21  8:51     ` Pantelis Antoniou
2017-09-21  9:10       ` Geert Uytterhoeven
     [not found]         ` <CAMuHMdU87p0xjtfOtaoHPcqZZxVvxJc-b1jdP_iJYBwHv1=ebw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-09-21  9:40           ` Pantelis Antoniou
2017-10-06  2:47     ` Vladimir Barinov
2017-10-06  7:20       ` Geert Uytterhoeven
     [not found]       ` <9635bb2d-8695-a168-d49e-0bd51807cc19-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
2017-10-06  9:18         ` Simon Horman
2017-10-09  7:18           ` Simon Horman
2017-10-10 16:16             ` Vladimir Barinov
2017-10-11  7:33               ` 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=CAMuHMdX-7MG2fCzJ-K5iQLnJcmZBaWjqMhmOhCxEemmWTh9pvw@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=catalin.marinas@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=horms@verge.net.au \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=mark.rutland@arm.com \
    --cc=pantelis.antoniou@konsulko.com \
    --cc=robh+dt@kernel.org \
    --cc=vladimir.barinov@cogentembedded.com \
    --cc=will.deacon@arm.com \
    /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;
as well as URLs for NNTP newsgroup(s).