Patch "PM / OPP: Move error message to debug level" has been added to the 4.9-stable tree
Subsystems (5)
This is a note to let you know that I've just added the patch titled
PM / OPP: Move error message to debug level
to the 4.9-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
pm-opp-move-error-message-to-debug-level.patch
and it can be found in the queue-4.9 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree, please let <[email protected]> know about it.
Quoted 1 line
From foo@baz Thu Dec 21 09:02:40 CET 2017
From: Fabio Estevam <[email protected]>
Date: Fri, 29 Sep 2017 14:39:49 -0300
Subject: PM / OPP: Move error message to debug level
From: Fabio Estevam <[email protected]>
[ Upstream commit 035ed07208dc501d023873447113f3f178592156 ]
On some i.MX6 platforms which do not have speed grading check, opp table will not be created in platform code, so cpufreq driver prints the following error message:
cpu cpu0: dev_pm_opp_get_opp_count: OPP table not found (-19)
However, this is not really an error in this case because the imx6q-cpufreq driver first calls dev_pm_opp_get_opp_count() and if it fails, it means that platform code does not provide OPP and then dev_pm_opp_of_add_table() will be called.
In order to avoid such confusing error message, move it to debug level.
It is up to the caller of dev_pm_opp_get_opp_count() to check its return value and decide if it will print an error or not.
--- drivers/base/power/opp/core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/base/power/opp/core.c +1 -1
@@ -331,7 +331,7 @@ int dev_pm_opp_get_opp_count(struct devi opp_table =_find_opp_table (dev);if (IS_ERR (opp_table)) { count =PTR_ERR (opp_table); -dev_err (dev,"%s: OPP table not found (%d)\n" , +dev_dbg (dev,"%s: OPP table not found (%d)\n" , __func__, count); goto out_unlock; }
Patches currently in stable-queue which might be from [email protected] are
queue-4.9/pm-opp-move-error-message-to-debug-level.patch