diff options
| author | Bin Meng <bmeng.cn@gmail.com> | 2018-10-24 06:36:38 -0700 |
|---|---|---|
| committer | Simon Glass <sjg@chromium.org> | 2018-11-14 09:16:28 -0800 |
| commit | e3245e4254e1e5caae24b33e203810db7307edfb (patch) | |
| tree | c729b8f28621344b4e32ad6cd7a6a93452a9a33e /drivers/nvme | |
| parent | ef329a6a736ba1bbfb940edc34ceaa14d3f45b53 (diff) | |
| download | u-boot-e3245e4254e1e5caae24b33e203810db7307edfb.zip u-boot-e3245e4254e1e5caae24b33e203810db7307edfb.tar.gz u-boot-e3245e4254e1e5caae24b33e203810db7307edfb.tar.bz2 | |
video: simplefb: 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>
Diffstat (limited to 'drivers/nvme')
0 files changed, 0 insertions, 0 deletions