[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPnjgZ0Bkk0Ock5_WQxsni+qNMQnWURrLLqfNFVfKczN6OgLoQ@mail.gmail.com>
Date: Sun, 17 Feb 2013 14:20:03 -0800
From: Simon Glass <sjg@...omium.org>
To: Hiroshi Doyu <hdoyu@...dia.com>
Cc: linux-tegra@...r.kernel.org, pdeschrijver@...dia.com,
pgaikwad@...dia.com, Grant Likely <grant.likely@...retlab.ca>,
Rob Herring <rob.herring@...xeda.com>,
Rob Landley <rob@...dley.net>,
Stephen Warren <swarren@...dotorg.org>,
Russell King <linux@....linux.org.uk>,
devicetree-discuss@...ts.ozlabs.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [v3 0/6] ARM: tegra: convert device tree files to use CLK defines
Hi Hiroshi,
On Fri, Feb 15, 2013 at 12:43 AM, Hiroshi Doyu <hdoyu@...dia.com> wrote:
> Hi,
>
> With new dtc+cpp feature, we could get rid of magic numbers in dts*
> files. This patch replaces CLK IDs.
>
> We also plan to share those DT header files with kernel source
> later[1].
>
> This series depends on:
> [PATCH 0/9] ARM: tegra: use new dtc+cpp feature
> http://lists.infradead.org/pipermail/linux-arm-kernel/2013-February/149613.html
>
> [5/6] and [6/6] depend on:
> [PATCH v6 00/10] Tegra114 clockframework
> http://lists.infradead.org/pipermail/linux-arm-kernel/2013-February/148895.html
>
> v2:
> http://lists.infradead.org/pipermail/linux-arm-kernel/2013-February/149816.html
>
> v1:
> http://lists.infradead.org/pipermail/linux-arm-kernel/2013-February/149672.html
>
> [1] http://lists.infradead.org/pipermail/linux-arm-kernel/2013-February/149804.html
>
>
> Hiroshi Doyu (6):
> ARM: tegra20: create a DT header defining CLK IDs
> ARM: tegra20: convert device tree files to use CLK defines
> ARM: tegra30: create a DT header defining CLK IDs
> ARM: tegra30: convert device tree files to use CLK defines
> ARM: tegra114: create a DT header defining CLK IDs
> ARM: tegra114: convert device tree files to use CLK defines
I wonder what sort of error message do you get when you make a mistake
in the .dts or one of the .dtsi includes? If cpp is handling the
including, does dtc just see a single file, in which case are the line
numbers printed with each error not much use? Or does dtc handle the
#line directives?
Just curious...
Regards,
Simon
>
> .../bindings/clock/nvidia,tegra114-car.txt | 261 +------------------
> .../bindings/clock/nvidia,tegra20-car.txt | 150 +----------
> .../bindings/clock/nvidia,tegra30-car.txt | 207 +--------------
> arch/arm/boot/dts/tegra114-car.h | 272 ++++++++++++++++++++
> arch/arm/boot/dts/tegra114.dtsip | 13 +-
> arch/arm/boot/dts/tegra20-car.h | 158 ++++++++++++
> arch/arm/boot/dts/tegra20-paz00.dtsp | 2 +-
> arch/arm/boot/dts/tegra20.dtsip | 85 +++---
> arch/arm/boot/dts/tegra30-car.h | 218 ++++++++++++++++
> arch/arm/boot/dts/tegra30.dtsip | 87 +++----
> 10 files changed, 746 insertions(+), 707 deletions(-)
> create mode 100644 arch/arm/boot/dts/tegra114-car.h
> create mode 100644 arch/arm/boot/dts/tegra20-car.h
> create mode 100644 arch/arm/boot/dts/tegra30-car.h
>
> --
> 1.7.9.5
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-tegra" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
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