Thread (53 messages) 53 messages, 8 authors, 2014-09-17

[PATCH 5/8] of: Add Tegra124 EMC bindings

From: Andrew Bresticker <hidden>
Date: 2014-07-11 16:43:40
Also in: linux-tegra, lkml

On Fri, Jul 11, 2014 at 7:18 AM, Mikko Perttunen [off-list ref] wrote:
Add binding documentation for the nvidia,tegra124-emc device tree
node.
quoted hunk ↗ jump to hunk
diff --git a/Documentation/devicetree/bindings/memory-controllers/tegra-emc.txt b/Documentation/devicetree/bindings/memory-controllers/tegra-emc.txt
+Required properties :
+- compatible : "nvidia,tegra124-emc".
+- reg : Should contain 1 or 2 entries:
+  - EMC register set
+  - MC register set : Required only if no node with
+    'compatible = "nvidia,tegra124-mc"' exists. The MC register set
+    is first read from the MC node. If it doesn't exist, it is read
+    from this property.
+- timings : Should contain 1 entry for each supported clock rate.
+  Entries should be named "timing at n" where n is a 0-based increasing
+  number. The timings must be listed in rate-ascending order.
There are upcoming boards which support multiple DRAM configurations
and require a separate set of timings for each configuration.  Could
we instead have multiple sets of timings with the proper one selected
at runtime by RAM code, as reported by PMC_STRAPPING_OPT_A_0?
Something like:

emc {
        emc-table at 0 {
                nvidia,ram-code = <0>;
                timing at 0 {
                        ...
                };
                ...
        };
        emc-table at 1 {
                nvidia,ram-code = <4>;
                timing at 0 {
                        ...
                };
                ...
        };
        ...
};
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help