From: Lokesh Vutla <lokeshvutla@ti.com>
Date: Mon, 9 Sep 2019 07:17:37 +0000 (+0530)
Subject: arm: k3: Fix getting ti_sci handle
X-Git-Tag: v2019.10-rc4~10^2~4
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=e8d3a186394893e6ee212be89c64e288109d28f1;p=platform%2Fkernel%2Fu-boot.git

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>
---

diff --git a/arch/arm/mach-k3/common.c b/arch/arm/mach-k3/common.c
index bab5ffd..3e36d90 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);