summaryrefslogtreecommitdiffstats
path: root/sound/oss/opl3.c
diff options
context:
space:
mode:
authorFabio Estevam <fabio.estevam@nxp.com>2017-09-29 14:39:49 -0300
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2017-10-11 01:51:15 +0200
commit035ed07208dc501d023873447113f3f178592156 (patch)
tree4626c7d044547e488ed223edd8268edb7c0a613c /sound/oss/opl3.c
parentd741029a2390406d4d94279ae5b346831a9e61e6 (diff)
downloadlinux-stable-035ed07208dc501d023873447113f3f178592156.tar.gz
linux-stable-035ed07208dc501d023873447113f3f178592156.tar.bz2
linux-stable-035ed07208dc501d023873447113f3f178592156.zip
PM / OPP: Move error message to debug level
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. Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'sound/oss/opl3.c')
0 files changed, 0 insertions, 0 deletions