From: Nicholas Lowell <nlowell@lexmark.com>
To: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
linux-kernel@vger.kernel.org
Cc: Nicholas Lowell <nlowell@lexmark.com>
Subject: [PATCH] regulator: giving regulator controlling gpios a non-empty label when used through the devicetree.
Date: Mon, 19 Mar 2018 09:23:14 -0400 [thread overview]
Message-ID: <1521465799-5589-1-git-send-email-nlowell@lexmark.com> (raw)
When the label is empty, it causes missing information and limits diagnostics
for instances such as 'cat /sys/kernel/debug/gpio'
Setting the label to the regulator supply_name will point to the device
using the gpio(s).
Signed-off-by: Nicholas Lowell <nlowell@lexmark.com>
---
drivers/regulator/gpio-regulator.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/regulator/gpio-regulator.c b/drivers/regulator/gpio-regulator.c
index 0fce06a..b1f00e2 100644
--- a/drivers/regulator/gpio-regulator.c
+++ b/drivers/regulator/gpio-regulator.c
@@ -196,6 +196,7 @@ of_get_gpio_regulator_config(struct device *dev, struct device_node *np,
break;
}
config->gpios[i].gpio = gpio;
+ config->gpios[i].label = config->supply_name;
if (proplen > 0) {
of_property_read_u32_index(np, "gpios-states",
i, &ret);
--
2.7.4
next reply other threads:[~2018-03-19 13:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 13:23 Nicholas Lowell [this message]
2018-03-20 1:22 ` Applied "regulator: giving regulator controlling gpios a non-empty label when used through the devicetree." to the regulator tree Mark Brown
[not found] <CANnE4YfYihuhAa8TtdzDB+MR2njSwszFRvr2g+h=mcRjD-DiiQ@mail.gmail.com>
2018-03-05 15:40 ` [PATCH] regulator: giving regulator controlling gpios a non-empty label when used through the devicetree 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=1521465799-5589-1-git-send-email-nlowell@lexmark.com \
--to=nlowell@lexmark.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
all inboxes | Powered by JetHome®