diff options
| author | Bin Meng <bmeng.cn@gmail.com> | 2018-10-10 22:06:58 -0700 |
|---|---|---|
| committer | Simon Glass <sjg@chromium.org> | 2018-11-14 09:16:27 -0800 |
| commit | 8d773c4ab3f77a5a6ceed974d00083a312454660 (patch) | |
| tree | 4b5411d76a591071a8f210833b6832ac03a18176 /doc/README.fuse | |
| parent | e601ab1bb69901420ba2c55d2f2d194a38739182 (diff) | |
| download | u-boot-8d773c4ab3f77a5a6ceed974d00083a312454660.tar.gz u-boot-8d773c4ab3f77a5a6ceed974d00083a312454660.tar.bz2 u-boot-8d773c4ab3f77a5a6ceed974d00083a312454660.zip | |
dm: core: Respect drivers with the DM_FLAG_PRE_RELOC flag in lists_bind_fdt()
Currently the comments of several APIs (eg: dm_init_and_scan()) say:
@pre_reloc_only: If true, bind only drivers with the DM_FLAG_PRE_RELOC
flag. If false bind all drivers.
The 'Pre-Relocation Support' chapter in doc/driver-model/README.txt
documents the same that both device tree properties and driver flag
are supported.
However the implementation only checks these special device tree
properties without checking the driver flag at all. This updates
lists_bind_fdt() to consider both scenarios.
Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
Squashed in http://patchwork.ozlabs.org/patch/996473/ :
Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'doc/README.fuse')
0 files changed, 0 insertions, 0 deletions