mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ninad Palsule <ninad@linux.ibm.com>
To: joel@jms.id.au, eajames@linux.ibm.com, lgirdwood@gmail.com,
	broonie@kernel.org, linux-kernel@vger.kernel.org,
	lakshmiy@us.ibm.com
Cc: Ninad Palsule <ninad@linux.ibm.com>
Subject: [PATCH v1] regulator: core: Convert warning to debug print
Date: Thu, 12 Oct 2023 12:42:35 -0500	[thread overview]
Message-ID: <20231012174235.2424670-1-ninad@linux.ibm.com> (raw)

There are some boards without the vcc regulators for eeprom or other
devices. In such cases, we should not see the following warning and
this confuses the user. We want to see this only when it is compiled
with CONFIG_REGULATOR_DEBUG option.

[0.747347] at24 6-0055: supply vcc not found, using dummy regulator
[0.752877] pca953x 6-0074: supply vcc not found, using dummy regulator

Signed-off-by: Ninad Palsule <ninad@linux.ibm.com>
---
 drivers/regulator/core.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c
index d8e1caaf207e..7d2e2495234e 100644
--- a/drivers/regulator/core.c
+++ b/drivers/regulator/core.c
@@ -2204,7 +2204,7 @@ struct regulator *_regulator_get(struct device *dev, const char *id,
 			 * enabled, even if it isn't hooked up, and just
 			 * provide a dummy.
 			 */
-			dev_warn(dev, "supply %s not found, using dummy regulator\n", id);
+			dev_dbg(dev, "supply %s not found, using dummy regulator\n", id);
 			rdev = dummy_regulator_rdev;
 			get_device(&rdev->dev);
 			break;
-- 
2.39.2


             reply	other threads:[~2023-10-12 17:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-12 17:42 Ninad Palsule [this message]
2023-10-12 17:47 ` Mark Brown
2023-10-12 21:45   ` Ninad Palsule
2023-10-13 15:38     ` Mark Brown
2023-10-16 12:24       ` Ninad Palsule

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=20231012174235.2424670-1-ninad@linux.ibm.com \
    --to=ninad@linux.ibm.com \
    --cc=broonie@kernel.org \
    --cc=eajames@linux.ibm.com \
    --cc=joel@jms.id.au \
    --cc=lakshmiy@us.ibm.com \
    --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

Powered by JetHome