With it its possible to use device tree overlays without having to use a per-platform overlay manager. Please see Documentation/devicetree/configfs-overlays.txt for more info. Changes since v2: - Removed ifdef CONFIG_OF_OVERLAY (since for now it's required) - Created a documentation entry -...
CONFIG_HAS_CUSTOM_SYS_INIT_SP_ADDR=y CONFIG_CUSTOM_SYS_INIT_SP_ADDR=0x800000 CONFIG_DEFAULT_DEVICE_TREE="rk3308-rock-pi-s" CONFIG_OF_LIBFDT_OVERLAY=y CONFIG_DM_RESET=y CONFIG_ROCKCHIP_RK3308=y CONFIG_SPL_DRIVERS_MISC=y Expand Down ...
DT-Overlay configfs interface (v8)"), but it was never used since then. Drop it to fix the below build error: drivers/of/configfs.c:46:21: error: ‘overlay_lock’ defined but not used [-Werror=unused-variable] 46 | static DEFINE_MUTEX(overlay_lock); | ^~~~ Signed-off-by: Kevi...
security implications of having direct access to the kernel's device tree. * To create an overlay you mkdir the directory: # mkdir /config/device-tree/overlays/foo * Either you echo the overlay firmware file to the path property file. # echo foo.dtbo >/config/device-tree/overlays/foo/path...