From: Mark Brown <broonie@kernel.org>
To: Dong Aisheng <aisheng.dong@nxp.com>
Cc: linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>
Subject: [PATCH 2/2] regulator: core: Allow dummy regulators for supplies
Date: Thu, 13 Apr 2017 19:03:16 +0100 [thread overview]
Message-ID: <20170413180316.617-2-broonie@kernel.org> (raw)
In-Reply-To: <20170413180316.617-1-broonie@kernel.org>
Rather than just not resolving the supply when there is explicitly no
supply mapping fall through and allow a dummy supply to be substituted.
Signed-off-by: Mark Brown <broonie@kernel.org>
---
drivers/regulator/core.c | 8 --------
1 file changed, 8 deletions(-)
diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c
index 2b464a286451..047ada74aa4a 100644
--- a/drivers/regulator/core.c
+++ b/drivers/regulator/core.c
@@ -1533,14 +1533,6 @@ static int regulator_resolve_supply(struct regulator_dev *rdev)
if (IS_ERR(r)) {
ret = PTR_ERR(r);
- if (ret == -ENODEV) {
- /*
- * No supply was specified for this regulator and
- * there will never be one.
- */
- return 0;
- }
-
/* Did the lookup explicitly defer for us? */
if (ret == -EPROBE_DEFER)
return ret;
--
2.11.0
next prev parent reply other threads:[~2017-04-13 18:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 18:03 [PATCH 1/2] regulator: core: Only propagate voltage changes to if it can change voltages Mark Brown
2017-04-13 18:03 ` Mark Brown [this message]
2017-04-14 13:44 ` [PATCH 2/2] regulator: core: Allow dummy regulators for supplies Dong Aisheng
2017-04-14 13:43 ` [PATCH 1/2] regulator: core: Only propagate voltage changes to if it can change voltages Dong Aisheng
2017-04-14 17:12 ` Applied "regulator: core: Only propagate voltage changes to if it can change voltages" to the regulator tree Mark Brown
2017-04-14 17:12 ` 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=20170413180316.617-2-broonie@kernel.org \
--to=broonie@kernel.org \
--cc=aisheng.dong@nxp.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