threeeye
bc1d038eac
Squashed backup commit (no shallow-clone history issues) of xiaomi-mt6833-dev/kernel_xiaomi_mt6833 (lineage-23.2 branch, upstream commit 9eece662e) plus all fixes applied to get everpal_defconfig building clean against a modern (GCC 15.2.0) toolchain -- see the previous commit message on the lineage-23.2 branch (also in this repo history is not available here since this is a squashed snapshot; full incremental history lives in the local DL380 checkout and the upstream GitHub remote). Upstream: https://github.com/xiaomi-mt6833-dev/kernel_xiaomi_mt6833 (lineage-23.2)
39 lines
1.1 KiB
Plaintext
39 lines
1.1 KiB
Plaintext
Samsung Exynos SYSRAM for SMP bringup:
|
|
------------------------------------
|
|
|
|
Samsung SMP-capable Exynos SoCs use part of the SYSRAM for the bringup
|
|
of the secondary cores. Once the core gets powered up it executes the
|
|
code that is residing at some specific location of the SYSRAM.
|
|
|
|
Therefore reserved section sub-nodes have to be added to the mmio-sram
|
|
declaration. These nodes are of two types depending upon secure or
|
|
non-secure execution environment.
|
|
|
|
Required sub-node properties:
|
|
- compatible : depending upon boot mode, should be
|
|
"samsung,exynos4210-sysram" : for Secure SYSRAM
|
|
"samsung,exynos4210-sysram-ns" : for Non-secure SYSRAM
|
|
|
|
The rest of the properties should follow the generic mmio-sram discription
|
|
found in Documentation/devicetree/bindings/sram/sram.txt
|
|
|
|
Example:
|
|
|
|
sysram@02020000 {
|
|
compatible = "mmio-sram";
|
|
reg = <0x02020000 0x54000>;
|
|
#address-cells = <1>;
|
|
#size-cells = <1>;
|
|
ranges = <0 0x02020000 0x54000>;
|
|
|
|
smp-sysram@0 {
|
|
compatible = "samsung,exynos4210-sysram";
|
|
reg = <0x0 0x1000>;
|
|
};
|
|
|
|
smp-sysram@53000 {
|
|
compatible = "samsung,exynos4210-sysram-ns";
|
|
reg = <0x53000 0x1000>;
|
|
};
|
|
};
|