From: Tomeu Vizoso <tomeu.vizoso@collabora.com>
To: linux-tegra@vger.kernel.org
Cc: Mikko Perttunen <mikko.perttunen@kapsi.fi>,
Tomeu Vizoso <tomeu.vizoso@collabora.com>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Stephen Warren <swarren@wwwdotorg.org>,
Thierry Reding <thierry.reding@gmail.com>,
Alexandre Courbot <gnurou@gmail.com>,
Eduardo Valentin <edubezval@gmail.com>,
Peter De Schrijver <pdeschrijver@nvidia.com>,
Paul Walmsley <paul@pwsan.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v7 02/18] of: Document long-ram-code property in nvidia,tegra20-apbmisc
Date: Wed, 11 Mar 2015 11:34:15 +0100 [thread overview]
Message-ID: <1426070126-26910-3-git-send-email-tomeu.vizoso@collabora.com> (raw)
In-Reply-To: <1426070126-26910-1-git-send-email-tomeu.vizoso@collabora.com>
Needed to properly decode the ram code register.
Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com>
---
v3: * Clarify wording as suggested by Mikko
---
Documentation/devicetree/bindings/misc/nvidia,tegra20-apbmisc.txt | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/misc/nvidia,tegra20-apbmisc.txt b/Documentation/devicetree/bindings/misc/nvidia,tegra20-apbmisc.txt
index 47b205c..4556359 100644
--- a/Documentation/devicetree/bindings/misc/nvidia,tegra20-apbmisc.txt
+++ b/Documentation/devicetree/bindings/misc/nvidia,tegra20-apbmisc.txt
@@ -10,3 +10,5 @@ Required properties:
The second entry gives the physical address and length of the
registers indicating the strapping options.
+Optional properties:
+- nvidia,long-ram-code: If present, the RAM code is long (4 bit). If not, short (2 bit).
--
2.1.0
next prev parent reply other threads:[~2015-03-11 10:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 10:34 [PATCH v7 00/18] Tegra124 EMC (external memory controller) support Tomeu Vizoso
2015-03-11 10:34 ` Tomeu Vizoso [this message]
2015-03-11 10:34 ` [PATCH v7 04/18] of: document new emc-timings subnode in nvidia,tegra124-car Tomeu Vizoso
2015-03-11 10:34 ` [PATCH v7 05/18] of: Document timings subnode of nvidia,tegra-mc Tomeu Vizoso
2015-03-11 10:34 ` [PATCH v7 06/18] of: Add Tegra124 EMC bindings Tomeu Vizoso
[not found] ` <1426070126-26910-1-git-send-email-tomeu.vizoso-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
2015-03-11 10:34 ` [PATCH v7 07/18] of: document external-memory-controller property in tegra124-car Tomeu Vizoso
2015-03-11 10:34 ` [PATCH v7 08/18] ARM: tegra: Add EMC to Tegra124 device tree Tomeu Vizoso
2015-03-11 10:34 ` [PATCH v7 16/18] ARM: tegra: Add EMC timings to Nyan Big " Tomeu Vizoso
2015-03-11 10:34 ` [PATCH v7 17/18] ARM: tegra: Add EMC timings to Nyan Blaze " Tomeu Vizoso
2015-03-11 10:34 ` [PATCH v7 09/18] ARM: tegra: Add EMC timings to Jetson TK1 " Tomeu Vizoso
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=1426070126-26910-3-git-send-email-tomeu.vizoso@collabora.com \
--to=tomeu.vizoso@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=edubezval@gmail.com \
--cc=galak@codeaurora.org \
--cc=gnurou@gmail.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mikko.perttunen@kapsi.fi \
--cc=paul@pwsan.com \
--cc=pawel.moll@arm.com \
--cc=pdeschrijver@nvidia.com \
--cc=robh+dt@kernel.org \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.com \
/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).