From: jacopo mondi <jacopo@jmondi.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Magnus Damm <magnus.damm@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Simon Horman <horms@verge.net.au>,
Jacopo Mondi <jacopo+renesas@jmondi.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/6] arm64: dts: renesas: r8a77965: Add "reg" properties
Date: Fri, 23 Feb 2018 13:22:50 +0100 [thread overview]
Message-ID: <20180223122250.GP7203@w540> (raw)
In-Reply-To: <CAMuHMdWGYpeOMJQKcT8=wm1YzQoB+vpK5H99Kg_pJ_HeBUw8Sw@mail.gmail.com>
Hi Geert,
On Fri, Feb 23, 2018 at 10:19:21AM +0100, Geert Uytterhoeven wrote:
> Hi Jacopo,
>
> On Thu, Feb 22, 2018 at 8:06 PM, Jacopo Mondi <jacopo+renesas@jmondi.org> wrote:
> > Add "reg" properties to place-holder nodes with unit address defined for
> > R-Car M3-N SoC.
> >
> > This silences the following DTC compiler warning:
> > Warning (unit_address_vs_reg): Node /soc/... has a unit name,
> > but no reg property
> >
> > Signed-off-by: Jacopo Mondi <jacopo+renesas@jmondi.org>
>
> A few minor nits below...
>
> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
>
> > --- a/arch/arm64/boot/dts/renesas/r8a77965.dtsi
> > +++ b/arch/arm64/boot/dts/renesas/r8a77965.dtsi
>
> > @@ -520,130 +521,163 @@
> > };
> >
> > avb: ethernet@e6800000 {
> > + reg = <0 0xe6800000 0 0x800>, <0 0xe6a00000 0 0x10000>;
>
> The first reg part would be sufficient for a placeholder.
> I think even setting the size to zero would work...
Not sure I fully got your point here.
Do you mean I have to remove the second (and third, fourth...) addresses range block
in all placeholder device nodes with multiple blocks (avb, du, rcar-sound) ?
Do you mean I have to set to 0 the address length in all placeholder nodes?
What's the point if they have to be added back once the device is
enabled?
>
> > du: display@feb00000 {
> > + reg = <0 0xfeb00000 0 0x70000>,
>
> Unlike M3-W, the M3-N DU has a third channel, so the size is too small.
>
Will fix in v2
> > + <0 0xfeb90000 0 0x14>;
> > /* placeholder */
>
> > @@ -703,38 +745,47 @@
> > };
> >
> > usb2_phy1: usb-phy@ee0a0200 {
> > + reg = <0 0xee0a0200 0 0x700>;
> > /* placeholder */
> > };
>
> To be moved up, next to the other usb2 devices?
Will add a patch to move this next to other usb2 device nodes in v2.
I will send v2 as soon as first review comment gets clarified.
Thanks
j
>
> 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
next prev parent reply other threads:[~2018-02-23 12:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 19:06 [PATCH 0/6] R-Car M3-N DTS fixes Jacopo Mondi
2018-02-22 19:06 ` [PATCH 1/6] arm64: dts: renesas: r8a77965: Add "reg" properties Jacopo Mondi
2018-02-23 9:19 ` Geert Uytterhoeven
2018-02-23 12:22 ` jacopo mondi [this message]
2018-02-23 12:34 ` Geert Uytterhoeven
2018-02-22 19:06 ` [PATCH 2/6] arm64: dts: renesas: r8a77965: Add #address-cells and #size-cells Jacopo Mondi
2018-02-23 9:23 ` Geert Uytterhoeven
2018-02-22 19:06 ` [PATCH 3/6] arm64: dts: renesas: r8a77965: Remove stale reg property Jacopo Mondi
2018-02-23 9:23 ` Geert Uytterhoeven
2018-02-22 19:06 ` [PATCH 4/6] arm64: dts: renesas: r8a77965: Add #phy-cells property Jacopo Mondi
2018-02-23 9:24 ` Geert Uytterhoeven
2018-02-22 19:06 ` [PATCH 5/6] arm64: dts: renesas: r8a77965: Add #pwm-cells property Jacopo Mondi
2018-02-23 9:25 ` Geert Uytterhoeven
2018-02-22 19:06 ` [PATCH 6/6] arm64: dts: renesas: r8a77965: Add #interrupt-cells property Jacopo Mondi
2018-02-23 9:27 ` Geert Uytterhoeven
2018-02-23 10:06 ` jacopo mondi
2018-02-23 12:02 ` 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=20180223122250.GP7203@w540 \
--to=jacopo@jmondi.org \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=jacopo+renesas@jmondi.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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 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).