[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141112142202.GB26488@ulmo>
Date: Wed, 12 Nov 2014 15:22:03 +0100
From: Thierry Reding <thierry.reding@...il.com>
To: Tomeu Vizoso <tomeu.vizoso@...labora.com>
Cc: linux-tegra@...r.kernel.org,
Javier Martinez Canillas <javier.martinez@...labora.co.uk>,
mikko.perttunen@...si.fi, acourbot@...dia.com,
Rob Herring <robh+dt@...nel.org>,
Pawel Moll <pawel.moll@....com>,
Mark Rutland <mark.rutland@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Kumar Gala <galak@...eaurora.org>,
Stephen Warren <swarren@...dotorg.org>,
Alexandre Courbot <gnurou@...il.com>,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 05/13] of: Document timings subnode of nvidia,tegra-mc
On Wed, Nov 12, 2014 at 08:56:28AM +0100, Tomeu Vizoso wrote:
[...]
> diff --git a/Documentation/devicetree/bindings/memory-controllers/nvidia,tegra-mc.txt b/Documentation/devicetree/bindings/memory-controllers/nvidia,tegra-mc.txt
[...]
> +Example board file:
> +
> +/ {
> + memory-controller@0,70019000 {
> + emc-timings-3 {
> + nvidia,ram-code = <3>;
I guess the alternative would be to keep the old names and simply use
the reg property instead of nvidia,ram-code to be compliant with best
practices in DT:
emc-timings@3 {
reg = <3>;
> +
> + timing-12750000 {
> + clock-frequency = <12750000>;
And:
timing@...50000 {
reg = <12750000>;
But I haven't been following this series too closely so far, so maybe
that had already been rejected.
Thierry
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists