From: Guenter Roeck <linux@roeck-us.net>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org,
Alan Tull <atull@opensource.altera.com>
Subject: Re: [PATCH] regulator: Ensure unique regulator debugfs directory names
Date: Mon, 17 Nov 2014 13:00:09 -0800 [thread overview]
Message-ID: <20141117210009.GA28122@roeck-us.net> (raw)
In-Reply-To: <1413559023-18293-1-git-send-email-linux@roeck-us.net>
On Fri, Oct 17, 2014 at 08:17:03AM -0700, Guenter Roeck wrote:
> If multiple regulator devices of the same type exist in a system,
> the regulator driver assigns generic names for the regulators it
> provides, and debugfs is enabled, the regulator subsystem attempts
> to create multiple entries with the same name in the regulator debugfs
> directory. This fails for all but the first regulator, resulting in
> multiple "Failed to create debugfs directory" log entries.
>
> To avoid the problem, prepend the debugfs directory name for a regulator
> with its parent device name if available, but only if no explicit
> regulator name was provided.
>
> Cc: Alan Tull <atull@opensource.altera.com>
> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
Hi Mark,
did you have time to look into this patch ?
Thanks,
Guenter
> ---
> drivers/regulator/core.c | 13 ++++++++++++-
> 1 file changed, 12 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c
> index cd87c0c..92f7a53 100644
> --- a/drivers/regulator/core.c
> +++ b/drivers/regulator/core.c
> @@ -3538,7 +3538,18 @@ static int add_regulator_attributes(struct regulator_dev *rdev)
>
> static void rdev_init_debugfs(struct regulator_dev *rdev)
> {
> - rdev->debugfs = debugfs_create_dir(rdev_get_name(rdev), debugfs_root);
> + struct device *parent = rdev->dev.parent;
> + const char *rname = rdev_get_name(rdev);
> + char name[NAME_MAX];
> +
> + /* Avoid duplicate debugfs directory names */
> + if (parent && rname == rdev->desc->name) {
> + snprintf(name, sizeof(name), "%s-%s", dev_name(parent),
> + rname);
> + rname = name;
> + }
> +
> + rdev->debugfs = debugfs_create_dir(rname, debugfs_root);
> if (!rdev->debugfs) {
> rdev_warn(rdev, "Failed to create debugfs directory\n");
> return;
> --
> 1.9.1
>
next prev parent reply other threads:[~2014-11-17 21:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 15:17 [PATCH] regulator: Ensure unique regulator debugfs directory names Guenter Roeck
2014-11-17 21:00 ` Guenter Roeck [this message]
2014-11-17 23:26 ` Mark Brown
2014-11-18 4:18 ` Guenter Roeck
2014-11-18 10:04 ` Mark Brown
2015-03-27 23:14 ` Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141117210009.GA28122@roeck-us.net \
--to=linux@roeck-us.net \
--cc=atull@opensource.altera.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).