core: device_bind_common: always use crypto node from U-Boot dtb

There is not crypto node in kernel dtb for early platform(such as
rk322x/rk3288/rk3368/rk3399, etc), so we decide to add crypto node
always in U-Boot dtb and ignore crypto node from kernel dtb.

This is a way to compatible with early platforms. Actually, we
need crypto during secure boot sequence, the crypto had better
not depends on kernel dtb.

Change-Id: Ibab4fca0741b45042b8d0868240449fb6b52aa14
Signed-off-by: Joseph Chen <chenjh@rock-chips.com>
This commit is contained in:
Joseph Chen 2019-05-29 09:47:37 +08:00 committed by Jianhong Chen
parent 48802b420e
commit ea4b8016c1
1 changed files with 1 additions and 1 deletions

View File

@ -71,7 +71,7 @@ static int device_bind_common(struct udevice *parent, const struct driver *drv,
list_for_each_entry_safe(dev, n, &uc->dev_head, uclass_node) {
if (!strcmp(name, dev->name) &&
dev_read_bool(dev, "u-boot,dm-pre-reloc")) {
if (drv->id == UCLASS_SERIAL) {
if (drv->id == UCLASS_SERIAL || drv->id == UCLASS_CRYPTO) {
/* Always use serial node from U-Boot dtb */
debug("%s do not delete uboot dev: %s\n",
__func__, dev->name);