summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorStephen Boyd <sboyd@codeaurora.org>2015-06-01 18:47:55 -0700
committerSrinivas Kandagatla <srinivas.kandagatla@linaro.org>2015-09-01 09:22:09 +0100
commit28b3a36b2e302c6aad518678c1f62177f1356a87 (patch)
treeabc63f8479791217fbde41abebee8e7dc68fcc1b
parent6b1f3530ab09928ad7f09219b9e3861f455a4c92 (diff)
downloadlinux-28b3a36b2e302c6aad518678c1f62177f1356a87.tar.gz
regulator: core: Print at debug level on debugfs creation failure
Failure to create a debugfs node is not an error, but we print a warning upon failure to create the node. Downgrade this to a debug printk so that we're quiet here. This allows multiple drivers to request a CPU's regulator so that CPUfreq and AVSish drivers can coexist. The downside of this approach is that whoever gets to debugfs first the others who come later to not have any debugfs attributes associated with them. Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
-rw-r--r--drivers/regulator/core.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c
index 78387a6cbae5..3c3137a43f63 100644
--- a/drivers/regulator/core.c
+++ b/drivers/regulator/core.c
@@ -1244,7 +1244,7 @@ static struct regulator *create_regulator(struct regulator_dev *rdev,
regulator->debugfs = debugfs_create_dir(regulator->supply_name,
rdev->debugfs);
if (!regulator->debugfs) {
- rdev_warn(rdev, "Failed to create debugfs directory\n");
+ rdev_dbg(rdev, "Failed to create debugfs directory\n");
} else {
debugfs_create_u32("uA_load", 0444, regulator->debugfs,
&regulator->uA_load);