Commit ad3a942b authored Jun 01, 2015 by Stephen Boyd Committed by Mark Brown Aug 14, 2015

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>
Signed-off-by: Mark Brown <broonie@kernel.org>

parent 1635e888

drivers/regulator/core.c

+1 −1

Original line number	Diff line number	Diff line
		@@ -1240,7 +1240,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);

Admin message