summaryrefslogtreecommitdiff
path: root/configs/kmcoge4_defconfig
diff options
context:
space:
mode:
authorBin Meng <bmeng.cn@gmail.com>2018-10-24 06:36:33 -0700
committerSimon Glass <sjg@chromium.org>2018-11-14 09:16:28 -0800
commitad0e8048437e776e687a977a84494852a64f4693 (patch)
tree011adec868e9135576025dbef3f6471f26ab3afa /configs/kmcoge4_defconfig
parent223b10ca7a6b1d35db9c775033895969b132ad56 (diff)
pinctrl: Remove DM_FLAG_PRE_RELOC flag in various drivers
When a driver declares DM_FLAG_PRE_RELOC flag, it wishes to be bound before relocation. However due to a bug in the DM core, the flag only takes effect when devices are statically declared via U_BOOT_DEVICE(). This bug has been fixed recently by commit "dm: core: Respect drivers with the DM_FLAG_PRE_RELOC flag in lists_bind_fdt()", but with the fix, it has a side effect that all existing drivers that declared DM_FLAG_PRE_RELOC flag will be bound before relocation now. This may expose potential boot failure on some boards due to insufficient memory during the pre-relocation stage. To mitigate this potential impact, the following changes are implemented: - Remove DM_FLAG_PRE_RELOC flag in the driver, if the driver only supports configuration from device tree (OF_CONTROL) - Keep DM_FLAG_PRE_RELOC flag in the driver only if the device is statically declared via U_BOOT_DEVICE() - Surround DM_FLAG_PRE_RELOC flag with OF_CONTROL check, for drivers that support both statically declared devices and configuration from device tree Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'configs/kmcoge4_defconfig')
0 files changed, 0 insertions, 0 deletions