[<prev] [next>] [day] [month] [year] [list]
Message-Id: <20191224144954.26152-1-tiny.windzz@gmail.com>
Date: Tue, 24 Dec 2019 14:49:54 +0000
From: Yangtao Li <tiny.windzz@...il.com>
To: cw00.choi@...sung.com, myungjoo.ham@...sung.com,
kyungmin.park@...sung.com, kgene@...nel.org, krzk@...nel.org,
linux-pm@...r.kernel.org, linux-samsung-soc@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Cc: Yangtao Li <tiny.windzz@...il.com>
Subject: [PATCH v2] PM / devfreq: exynos-bus: Add error log when fail to get devfreq-event
Adding an error log makes it easier to trace the function's error path.
Because the error code may be rewritten on return, print error code here.
Signed-off-by: Yangtao Li <tiny.windzz@...il.com>
---
v2:
-update subject and fix over 80 char
---
drivers/devfreq/exynos-bus.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/devfreq/exynos-bus.c b/drivers/devfreq/exynos-bus.c
index 948e9340f91c..a4c6187b1eac 100644
--- a/drivers/devfreq/exynos-bus.c
+++ b/drivers/devfreq/exynos-bus.c
@@ -126,6 +126,9 @@ static int exynos_bus_get_dev_status(struct device *dev,
ret = exynos_bus_get_event(bus, &edata);
if (ret < 0) {
+ dev_err(dev,
+ "failed to get event from devfreq-event devices %d\n",
+ ret);
stat->total_time = stat->busy_time = 0;
goto err;
}
--
2.17.1
Powered by blists - more mailing lists