From: Pantelis Antoniou <pantelis.antoniou-OWPKS81ov/FWk0Htik3J/w@public.gmane.org>
To: Geert Uytterhoeven <geert-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org>
Cc: Vladimir Barinov
<vladimir.barinov-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>,
Simon Horman <horms-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>,
Magnus Damm <magnus.damm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
Catalin Marinas <catalin.marinas-5wv7dgnIgG8@public.gmane.org>,
Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Linux-Renesas
<linux-renesas-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH v2 04/18] arm64: dts: m3ulcb-kf: initial device tree
Date: Thu, 21 Sep 2017 12:40:55 +0300 [thread overview]
Message-ID: <1505986855.23573.80.camel@hp800z> (raw)
In-Reply-To: <CAMuHMdU87p0xjtfOtaoHPcqZZxVvxJc-b1jdP_iJYBwHv1=ebw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Hi Geert,
On Thu, 2017-09-21 at 11:10 +0200, Geert Uytterhoeven wrote:
> Hi Pantelis,
>
> On Thu, Sep 21, 2017 at 10:51 AM, Pantelis Antoniou
> <pantelis.antoniou-OWPKS81ov/FWk0Htik3J/w@public.gmane.org> wrote:
> > On Wed, 2017-09-20 at 14:32 +0200, Geert Uytterhoeven wrote:
> >> On Thu, Sep 14, 2017 at 4:18 PM, Vladimir Barinov
> >> <vladimir.barinov-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org> wrote:
> >> > +#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.
> >>
> >
> > Sigh, yes.
> >
> >> > +/ {
> >> > + 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?
> >
> > You can hack something in DT but it will be gross indeed.
> >
> > Ideally you'd want a += operator, but it's going to take a lot of
> > changes starting from DTB blob format.
> >
> > In yaml we could easily do this with an append tag type
> >
> > compatible: [ "renesas,m3ulcb", "renesas,r8a7796" ]
> >
> > compatible: !append "shimafuji,kingfisher"
>
> As we already have /delete-property/, we could add /append-property/ and
> /prepend-property/? Would be useful for a .dts including and enhancing
> an .dtsi, too.
>
Yes, that would work on the DTS source level. Doesn't help at runtime.
> That doesn't solve the DTB blob format issue yet, though.
>
Right. The tree and property deletion commands do not have a mapping to
the DTB format. You could add special characters to a property name and
have the overlay application code do something about it.
For instance the original overlay submission did support property and
node deletion by using '-property' & '-node'. Alas it was removed.
> > Are you going to be at ELCE? I have a bunch of thing to ask you about
> > your DT usage patterns.
>
> Yes, and registered for the Device Tree Workshop.
>
Great. See you then.
> Gr{oetje,eeting}s,
>
> Geert
>
Regards
-- Pantelis
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.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
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-09-21 9:40 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
[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 [this message]
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=1505986855.23573.80.camel@hp800z \
--to=pantelis.antoniou-owpks81ov/fwk0htik3j/w@public.gmane.org \
--cc=catalin.marinas-5wv7dgnIgG8@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=geert-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org \
--cc=horms-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org \
--cc=linux-renesas-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=magnus.damm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=vladimir.barinov-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org \
--cc=will.deacon-5wv7dgnIgG8@public.gmane.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;
as well as URLs for NNTP newsgroup(s).