diff options
| author | Lokesh Vutla <lokeshvutla@ti.com> | 2019-09-09 12:47:37 +0530 |
|---|---|---|
| committer | Tom Rini <trini@konsulko.com> | 2019-09-13 11:56:30 -0400 |
| commit | e8d3a186394893e6ee212be89c64e288109d28f1 (patch) | |
| tree | ea10c76512529902f87f42857c0929e3504723cd /arch/arm/mach-k3/common.c | |
| parent | b8879c4ef7c0b569a2b1add6b7af98b44032217b (diff) | |
| download | u-boot-e8d3a186394893e6ee212be89c64e288109d28f1.tar.gz u-boot-e8d3a186394893e6ee212be89c64e288109d28f1.tar.xz u-boot-e8d3a186394893e6ee212be89c64e288109d28f1.zip | |
arm: k3: Fix getting ti_sci handle
API get_ti_sci_handle() is relying on the device-tree node name
to be "dmsc" for probing the ti_sci device. But with the introduction
of debug messages for dmsc, the node name changed to dmsc@44083000.
Because of this ti_sci is never probed cause a boot failure. Instead
of relying on device-tree node name, use the first available firmware
node for probing ti_sci.
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Diffstat (limited to 'arch/arm/mach-k3/common.c')
| -rw-r--r-- | arch/arm/mach-k3/common.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/arm/mach-k3/common.c b/arch/arm/mach-k3/common.c index bab5ffdf40..3e36d90ace 100644 --- a/arch/arm/mach-k3/common.c +++ b/arch/arm/mach-k3/common.c @@ -20,7 +20,7 @@ struct ti_sci_handle *get_ti_sci_handle(void) struct udevice *dev; int ret; - ret = uclass_get_device_by_name(UCLASS_FIRMWARE, "dmsc", &dev); + ret = uclass_get_device(UCLASS_FIRMWARE, 0, &dev); if (ret) panic("Failed to get SYSFW (%d)\n", ret); |