All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Biju Das <biju.das@bp.renesas.com>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Simon Horman <horms@verge.net.au>,
	Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Magnus Damm <magnus.damm@gmail.com>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
	<devicetree@vger.kernel.org>,
	Chris Paterson <Chris.Paterson2@renesas.com>,
	Fabrizio Castro <fabrizio.castro@bp.renesas.com>
Subject: Re: [PATCH 1/8] arm64: dts: renesas: hihope-common: Move du clk properties out of common dtsi
Date: Tue, 1 Oct 2019 20:17:53 +0200	[thread overview]
Message-ID: <CAMuHMdVHFmcC16jgnwmf2225VqqahxJ-ipwOTZoinShgVYnHyw@mail.gmail.com> (raw)
In-Reply-To: <20191001181134.GC4735@pendragon.ideasonboard.com>

Hi Laurent,

On Tue, Oct 1, 2019 at 8:11 PM Laurent Pinchart
<laurent.pinchart@ideasonboard.com> wrote:
> On Tue, Oct 01, 2019 at 01:15:17PM +0100, Biju Das wrote:
> > RZ/G2N board is pin compatible with RZ/G2M board. However on the SoC
> > side RZ/G2N uses DU3 where as RZ/G2M uses DU2 for the DPAD. In order to
> > reuse the common dtsi for both the boards, it is required to move du clock
> > properties from common dtsi to board specific dts.
> >
> > Signed-off-by: Biju Das <biju.das@bp.renesas.com>
>
> It would be nice if DT had a syntax that allowed extending an existing
> property. It would allow us to write
>
> &du {
>         clocks += <&versaclock5 1>,
>                   <&x302_clk>,
>                   <&versaclock5 2>;
>         clock-names += "dclkin.0", "dclkin.1", "dclkin.2";
> };
>
> in hihope-common.dtsi and be done with it.
>
> Rob, do you think that's something worth adding ?

Yeah, we already have /delete-property/, but not yet /append-property/.

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:[~2019-10-01 18:18 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-01 12:15 [PATCH 0/8] Add Display support Biju Das
2019-10-01 12:15 ` [PATCH 1/8] arm64: dts: renesas: hihope-common: Move du clk properties out of common dtsi Biju Das
2019-10-01 18:11   ` Laurent Pinchart
2019-10-01 18:17     ` Geert Uytterhoeven [this message]
2019-10-01 12:15 ` [PATCH 2/8] arm64: dts: renesas: r8a774b1: Add DU device to DT Biju Das
2019-10-01 18:13   ` Laurent Pinchart
2019-10-01 12:15 ` [PATCH 3/8] arm64: dts: renesas: r8a774b1: Add HDMI encoder instance Biju Das
2019-10-01 18:15   ` Laurent Pinchart
2019-10-01 12:15 ` [PATCH 4/8] arm64: dts: renesas: r8a774b1-hihope-rzg2n: Add display clock properties Biju Das
2019-10-01 18:15   ` Laurent Pinchart
2019-10-01 12:15 ` [PATCH 5/8] arm64: dts: renesas: r8a774b1: Add FDP1 device nodes Biju Das
2019-10-01 18:16   ` Laurent Pinchart
2019-10-01 12:15 ` [PATCH 6/8] arm64: dts: renesas: r8a774b1: Add PWM " Biju Das
2019-10-01 18:17   ` Laurent Pinchart
2019-10-01 12:15 ` [PATCH 7/8] arm64: dts: renesas: hihope-rzg2-ex: Enable backlight Biju Das
2019-10-01 18:18   ` Laurent Pinchart
2019-10-01 12:15 ` [PATCH 8/8] arm64: dts: renesas: hihope-rzg2-ex: Add LVDS panel support Biju Das
2019-10-01 18:25   ` Laurent Pinchart
2019-10-02  8:30     ` Biju Das

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=CAMuHMdVHFmcC16jgnwmf2225VqqahxJ-ipwOTZoinShgVYnHyw@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=Chris.Paterson2@renesas.com \
    --cc=biju.das@bp.renesas.com \
    --cc=devicetree@vger.kernel.org \
    --cc=fabrizio.castro@bp.renesas.com \
    --cc=geert+renesas@glider.be \
    --cc=horms@verge.net.au \
    --cc=kieran.bingham+renesas@ideasonboard.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.