From: Fabio Estevam <feste...@denx.de>
dev_info() message is not printed by default. Increase the log level
to dev_crit(). This allows the critical messages related to the temperature
getting beyong the alert threshold to be displayed.
Signed-off-by: Fabio Estevam <feste...@denx.de>
---
Changes since v1:
- Use dev_crit() instead of selecting LOG via Kconfig. (Tom)
drivers/thermal/imx_tmu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/thermal/imx_tmu.c b/drivers/thermal/imx_tmu.c
index d9a04eaf79fb..d2ea084d2d2f 100644
--- a/drivers/thermal/imx_tmu.c
+++ b/drivers/thermal/imx_tmu.c
@@ -238,7 +238,7 @@ int imx_tmu_get_temp(struct udevice *dev, int *temp)
return ret;
while (cpu_tmp >= pdata->alert) {
- dev_info(dev, "CPU Temperature (%dC) has beyond alert (%dC),
close to critical (%dC) waiting...\n",
+ dev_crit(dev, "CPU Temperature (%dC) has beyond alert (%dC),
close to critical (%dC) waiting...\n",
cpu_tmp, pdata->alert, pdata->critical);
mdelay(pdata->polling_delay);
ret = read_temperature(dev, &cpu_tmp);
--
2.34.1
