From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH 0/7] arm: dts: renesas: Group tuples in reg/ranges/dma-ranges/states properties
Date: Fri, 13 Dec 2019 17:41:07 +0100 [thread overview]
Message-ID: <20191213164115.3697-1-geert+renesas@glider.be> (raw)
Hi all,
To improve human readability and enable automatic validation, tuples
in various properties should be grouped. While "make dtbs_check" does
not impose this yet for all properties, it does for some, hence
triggering me to fix (I hope) all of them.
Unfortunately even after this, a few "... is too long" warnings are
still printed (e.g. for PCI "ranges"), which I believe are false
positives.
This series is against renesas-devel-2019-12-13-v5.5-rc1[*] with
"[PATCH] ARM: dts: rcar-gen2: Fix PCI high address in
interrupt-map-mask" applied on top.
Thanks for your comments!
[*] Will be pushed out when gitolite.kernel.org is back.
Geert Uytterhoeven (7):
ARM: dts: renesas: Group tuples in regulator-gpio states properties
ARM: dts: renesas: Group tuples in interrupt properties
ARM: dts: renesas: Group tuples in pci ranges and dma-ranges
properties
arm64: dts: renesas: Group tuples in regulator-gpio states properties
arm64: dts: renesas: Group tuples in interrupt properties
arm64: dts: renesas: Group tuples in pci ranges and dma-ranges
properties
arm64: dts: renesas: r8a77970: Group tuples in thermal reg property
arch/arm/boot/dts/iwg20d-q7-common.dtsi | 3 +-
arch/arm/boot/dts/r7s72100.dtsi | 18 +-
arch/arm/boot/dts/r8a73a4.dtsi | 42 ++--
arch/arm/boot/dts/r8a7740-armadillo800eva.dts | 3 +-
arch/arm/boot/dts/r8a7740.dtsi | 102 ++++-----
arch/arm/boot/dts/r8a7743.dtsi | 152 ++++++-------
arch/arm/boot/dts/r8a7744.dtsi | 152 ++++++-------
arch/arm/boot/dts/r8a7745-iwg22d-sodimm.dts | 3 +-
arch/arm/boot/dts/r8a7745.dtsi | 112 ++++-----
arch/arm/boot/dts/r8a77470-iwg23s-sbc.dts | 3 +-
arch/arm/boot/dts/r8a77470.dtsi | 80 +++----
arch/arm/boot/dts/r8a7778.dtsi | 8 +-
arch/arm/boot/dts/r8a7779-marzen.dts | 3 +-
arch/arm/boot/dts/r8a7779.dtsi | 8 +-
arch/arm/boot/dts/r8a7790-lager.dts | 6 +-
arch/arm/boot/dts/r8a7790.dtsi | 158 ++++++-------
arch/arm/boot/dts/r8a7791-koelsch.dts | 9 +-
arch/arm/boot/dts/r8a7791-porter.dts | 6 +-
arch/arm/boot/dts/r8a7791.dtsi | 152 ++++++-------
arch/arm/boot/dts/r8a7792.dtsi | 64 +++---
arch/arm/boot/dts/r8a7793-gose.dts | 9 +-
arch/arm/boot/dts/r8a7793.dtsi | 120 +++++-----
arch/arm/boot/dts/r8a7794-alt.dts | 6 +-
arch/arm/boot/dts/r8a7794-silk.dts | 3 +-
arch/arm/boot/dts/r8a7794.dtsi | 104 ++++-----
arch/arm/boot/dts/sh73a0.dtsi | 122 +++++-----
.../arm64/boot/dts/renesas/hihope-common.dtsi | 3 +-
arch/arm64/boot/dts/renesas/r8a774a1.dtsi | 206 ++++++++---------
arch/arm64/boot/dts/renesas/r8a774b1.dtsi | 206 ++++++++---------
.../boot/dts/renesas/r8a774c0-cat874.dts | 3 +-
arch/arm64/boot/dts/renesas/r8a774c0.dtsi | 164 +++++++-------
arch/arm64/boot/dts/renesas/r8a7795.dtsi | 214 +++++++++---------
arch/arm64/boot/dts/renesas/r8a77960.dtsi | 206 ++++++++---------
arch/arm64/boot/dts/renesas/r8a77965.dtsi | 206 ++++++++---------
arch/arm64/boot/dts/renesas/r8a77970.dtsi | 52 ++---
arch/arm64/boot/dts/renesas/r8a77980.dtsi | 96 ++++----
.../arm64/boot/dts/renesas/r8a77990-ebisu.dts | 6 +-
arch/arm64/boot/dts/renesas/r8a77990.dtsi | 164 +++++++-------
arch/arm64/boot/dts/renesas/r8a77995.dtsi | 74 +++---
.../boot/dts/renesas/salvator-common.dtsi | 6 +-
arch/arm64/boot/dts/renesas/ulcb.dtsi | 3 +-
41 files changed, 1514 insertions(+), 1543 deletions(-)
--
2.17.1
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 reply other threads:[~2019-12-13 20:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-13 16:41 Geert Uytterhoeven [this message]
2019-12-13 16:41 ` [PATCH 1/7] ARM: dts: renesas: Group tuples in regulator-gpio states properties Geert Uytterhoeven
2019-12-13 16:41 ` [PATCH] ARM: dts: sh73a0: Add missing clock-frequency for fixed clocks Geert Uytterhoeven
2019-12-13 16:41 ` [PATCH 2/7] ARM: dts: renesas: Group tuples in interrupt properties Geert Uytterhoeven
2019-12-13 16:41 ` [PATCH 3/7] ARM: dts: renesas: Group tuples in pci ranges and dma-ranges properties Geert Uytterhoeven
2019-12-13 16:41 ` [PATCH 4/7] arm64: dts: renesas: Group tuples in regulator-gpio states properties Geert Uytterhoeven
2019-12-13 16:41 ` [PATCH 5/7] arm64: dts: renesas: Group tuples in interrupt properties Geert Uytterhoeven
2019-12-13 16:41 ` [PATCH 6/7] arm64: dts: renesas: Group tuples in pci ranges and dma-ranges properties Geert Uytterhoeven
2019-12-13 16:41 ` [PATCH 7/7] arm64: dts: renesas: r8a77970: Group tuples in thermal reg property Geert Uytterhoeven
2019-12-14 7:08 ` [PATCH 0/7] arm: dts: renesas: Group tuples in reg/ranges/dma-ranges/states properties Ulrich Hecht
2019-12-20 15:51 ` 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=20191213164115.3697-1-geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=devicetree@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).