diff options
| author | Bin Meng <bmeng.cn@gmail.com> | 2018-10-24 06:36:28 -0700 |
|---|---|---|
| committer | Simon Glass <sjg@chromium.org> | 2018-11-14 09:16:28 -0800 |
| commit | 4854ebc57e88f371963b5fa12587a3dd5e116e79 (patch) | |
| tree | c8cbf6c6d7522c30f6877e5276826ed3e5e7932b /disk | |
| parent | 6f57c34473d37b8da5e6a3764d0d377d748aeef1 (diff) | |
| download | u-boot-4854ebc57e88f371963b5fa12587a3dd5e116e79.zip u-boot-4854ebc57e88f371963b5fa12587a3dd5e116e79.tar.gz u-boot-4854ebc57e88f371963b5fa12587a3dd5e116e79.tar.bz2 | |
arm: stm32mp: Remove DM_FLAG_PRE_RELOC flag
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>
Reviewed-by: Patrick Delaunay <patrick.delaunay@st.com>
Diffstat (limited to 'disk')
0 files changed, 0 insertions, 0 deletions