From: Javier Martinez Canillas <javier@osg.samsung.com>
To: linux-kernel@vger.kernel.org
Cc: devicetree@vger.kernel.org, Heiko Stuebner <heiko@sntech.de>,
linux-rockchip@lists.infradead.org,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel@lists.infradead.org,
Javier Martinez Canillas <javier@osg.samsung.com>
Subject: [PATCH 4/8] ARM: dts: rockchip: Remove skeleton.dtsi inclusion in rk3xxx.dtsi
Date: Fri, 9 Sep 2016 10:01:05 -0400 [thread overview]
Message-ID: <1473429669-6185-5-git-send-email-javier@osg.samsung.com> (raw)
In-Reply-To: <1473429669-6185-1-git-send-email-javier@osg.samsung.com>
The skeleton.dtsi file was removed in ARM64 for different reasons as
explained in commit ("3ebee5a2e141 arm64: dts: kill skeleton.dtsi").
These also applies to ARM and it will also allow to get rid of the
following DTC warnings in the future:
"Node /memory has a reg or ranges property, but no unit name"
The disassembled DTB are almost the same, besides empty chosen nodes
being removed. So the change should not have a functional impact.
Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com>
---
arch/arm/boot/dts/rk3xxx.dtsi | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/rk3xxx.dtsi b/arch/arm/boot/dts/rk3xxx.dtsi
index e15beb3c671e..0394312f392d 100644
--- a/arch/arm/boot/dts/rk3xxx.dtsi
+++ b/arch/arm/boot/dts/rk3xxx.dtsi
@@ -44,9 +44,11 @@
#include <dt-bindings/interrupt-controller/irq.h>
#include <dt-bindings/interrupt-controller/arm-gic.h>
#include <dt-bindings/soc/rockchip,boot-mode.h>
-#include "skeleton.dtsi"
/ {
+ #address-cells = <1>;
+ #size-cells = <1>;
+
interrupt-parent = <&gic>;
aliases {
--
2.7.4
next prev parent reply other threads:[~2016-09-09 14:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-09 14:01 [PATCH 0/8] ARM: dts: rockchip: Remove skeleton.dtsi usage and fix memory node DTC warnings Javier Martinez Canillas
2016-09-09 14:01 ` [PATCH 1/8] ARM: dts: rockchip: Remove skeleton.dtsi inclusion in rk3036.dtsi Javier Martinez Canillas
[not found] ` <1473429669-6185-1-git-send-email-javier-JPH+aEBZ4P+UEJcrhfAQsw@public.gmane.org>
2016-09-09 14:01 ` [PATCH 2/8] ARM: dts: rockchip: Remove skeleton.dtsi inclusion in rk322x.dtsi Javier Martinez Canillas
2016-09-09 14:01 ` [PATCH 6/8] ARM: dts: rockchip: Add missing unit name to memory nodes in rk322x boards Javier Martinez Canillas
2016-09-10 21:51 ` [PATCH 0/8] ARM: dts: rockchip: Remove skeleton.dtsi usage and fix memory node DTC warnings Heiko Stuebner
2016-09-09 14:01 ` [PATCH 3/8] ARM: dts: rockchip: Remove skeleton.dtsi inclusion in rk3288.dtsi Javier Martinez Canillas
2016-09-09 14:01 ` Javier Martinez Canillas [this message]
2016-09-09 14:01 ` [PATCH 5/8] ARM: dts: rockchip: Add missing unit name to memory nodes in rk3036 boards Javier Martinez Canillas
2016-09-09 14:01 ` [PATCH 7/8] ARM: dts: rockchip: Add missing unit name to memory nodes in rk3288 boards Javier Martinez Canillas
2016-09-09 14:01 ` [PATCH 8/8] ARM: dts: rockchip: Add missing unit name to memory nodes in rk3xxx boards Javier Martinez Canillas
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=1473429669-6185-5-git-send-email-javier@osg.samsung.com \
--to=javier@osg.samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--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