IoT Board Modify Reserved-Memory
Answer.
Because the IoT Board does not use display-related content, you can remove the display-related content in the device tree and add reserved-memory.
Currently, the reserved-memory of 128M is 19980k, and the reserved-memory of 512M is 117404K.
Delete display-related content from reserved-memory in the device tree: output/build/linux-custom/arm64/boot/dts/nuvoton/ma35d1.dtsi
Code: Select all
reserved-memory {
#address-cells = <2>;
#size-cells = <2>;
ranges;
display_buf: display_buf@0 {
reg = <0x0 0x8C800000 0x0 0x3000000>; /*48MiB*/
no-map;
};
vc8k_buf: vc8k_buf@0 {
reg = <0x0 0x8A800000 0x0 0x2000000>; /*32MiB*/
no-map;
};
gc520l_buf: gc520l_buf@0 {
reg = <0x0 0x8A000000 0x0 0x800000>; /*8MiB*/
no-map;
};
rproc_buf: rproc_buf@0 {
reg = <0x0 0x80020000 0x0 0x60000>; /*384KB*/
no-map;
};
};
Code: Select all
reserved-memory {
#address-cells = <2>;
#size-cells = <2>;
ranges;
rproc_buf: rproc_buf@0 {
reg = <0x0 0x80020000 0x0 0x60000>; /*384KB*/
no-map;
};
};
Put the following content:
Code: Select all
# SPDX-License-Identifier: GPL-2.0
dtb-$(CONFIG_ARCH_MA35D1) += ma35d1-iot-128m.dtb \
ma35d1-iot-256m.dtb \
ma35d1-iot-512m.dtb \
ma35d1-som-256m.dtb \
ma35d1-som-512m.dtb \
ma35d1-som-1g.dtb
always := $(dtb-y)
clean-files := *.dtb
Code: Select all
# SPDX-License-Identifier: GPL-2.0
dtb-$(CONFIG_ARCH_MA35D1) += ma35d1-iot-512m.dtb
always := $(dtb-y)
clean-files := *.dtb
#MA35D1, #IoT, #Reserved-Memory
.