Re: [PATCH v2 02/12] of: Document long-ram-code property in nvidia,tegra20-apbmisc

From: Mikko Perttunen
Date: Wed Oct 22 2014 - 03:39:33 EST


On 10/21/2014 05:45 PM, Tomeu Vizoso wrote:
Needed to properly decode the ram code register.

Signed-off-by: Tomeu Vizoso <tomeu.vizoso@xxxxxxxxxxxxx>
---
Documentation/devicetree/bindings/misc/nvidia,tegra20-apbmisc.txt | 3 +++
1 file changed, 3 insertions(+)

diff --git a/Documentation/devicetree/bindings/misc/nvidia,tegra20-apbmisc.txt b/Documentation/devicetree/bindings/misc/nvidia,tegra20-apbmisc.txt
index b97b8be..e2562ed 100644
--- a/Documentation/devicetree/bindings/misc/nvidia,tegra20-apbmisc.txt
+++ b/Documentation/devicetree/bindings/misc/nvidia,tegra20-apbmisc.txt
@@ -11,3 +11,6 @@ Required properties:
The second entry gives the physical address and length of the
registers indicating the strapping options.

+Optional properties:
+- nvidia,long-ram-code: boolean that tells whether the ram code is long (4 bit)
+ or short (2 bit). If not present, false.


I think just "If present, the RAM code is long (4 bit). If not, short (2 bit)" would be clearer, as the booleanness of this property is not really present in the device tree file.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/