Commit | Line | Data |
---|---|---|
d7067f1c SK |
1 | Samsung Exynos SYSRAM for SMP bringup: |
2 | ------------------------------------ | |
3 | ||
4 | Samsung SMP-capable Exynos SoCs use part of the SYSRAM for the bringup | |
5 | of the secondary cores. Once the core gets powered up it executes the | |
6 | code that is residing at some specific location of the SYSRAM. | |
7 | ||
8 | Therefore reserved section sub-nodes have to be added to the mmio-sram | |
9 | declaration. These nodes are of two types depending upon secure or | |
10 | non-secure execution environment. | |
11 | ||
12 | Required sub-node properties: | |
13 | - compatible : depending upon boot mode, should be | |
14 | "samsung,exynos4210-sysram" : for Secure SYSRAM | |
15 | "samsung,exynos4210-sysram-ns" : for Non-secure SYSRAM | |
16 | ||
17 | The rest of the properties should follow the generic mmio-sram discription | |
18 | found in ../../misc/sysram.txt | |
19 | ||
20 | Example: | |
21 | ||
22 | sysram@02020000 { | |
23 | compatible = "mmio-sram"; | |
24 | reg = <0x02020000 0x54000>; | |
25 | #address-cells = <1>; | |
26 | #size-cells = <1>; | |
27 | ranges = <0 0x02020000 0x54000>; | |
28 | ||
29 | smp-sysram@0 { | |
30 | compatible = "samsung,exynos4210-sysram"; | |
31 | reg = <0x0 0x1000>; | |
32 | }; | |
33 | ||
34 | smp-sysram@53000 { | |
35 | compatible = "samsung,exynos4210-sysram-ns"; | |
36 | reg = <0x53000 0x1000>; | |
37 | }; | |
38 | }; |