[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1431596142.2881.13.camel@linaro.org>
Date: Thu, 14 May 2015 10:35:42 +0100
From: "Jon Medhurst (Tixy)" <tixy@...aro.org>
To: Liviu Dudau <Liviu.Dudau@....com>
Cc: Arnd Bergmann <arnd@...db.de>, Olof Johansson <olof@...om.net>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Marc Zyngier <marc.zyngier@....com>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will.deacon@....com>,
Sudeep Holla <sudeep.holla@....com>,
devicetree <devicetree@...r.kernel.org>,
LAKML <linux-arm-kernel@...ts.infradead.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/5] arm64: Juno: Split juno.dts into juno-base.dtsi and
juno.dts.
On Wed, 2015-05-13 at 18:11 +0100, Liviu Dudau wrote:
> Prepare the device tree for adding more boards based on Juno r0.
>
> Signed-off-by: Liviu Dudau <Liviu.Dudau@....com>
> ---
> arch/arm64/boot/dts/arm/juno-base.dtsi | 125 +++++++++++++++++++++++++++++++++
> arch/arm64/boot/dts/arm/juno.dts | 122 +-------------------------------
What criteria were used to select the contents of juno-base.dtsi?
>From what I can see, the stuff left out of base is still the same for r0
and r1 (cpu, pmu, memory, psci!). And so juno-r1.dts could just be
-------------------------------------------------------------------------
#include "juno.dts"
/ {
model = "ARM Juno development board (r1)";
};
&memtimer {
status = "okay";
};
-------------------------------------------------------------------------
Yes, it's a bit hacky, but avoids duplication of source code.
I can only assume there are come non-public differences between r0 and
r1?
--
Tixy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists