mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ninad Palsule <ninad@linux.ibm.com>
To: Mark Brown <broonie@kernel.org>
Cc: joel@jms.id.au, eajames@linux.ibm.com, lgirdwood@gmail.com,
	linux-kernel@vger.kernel.org, lakshmiy@us.ibm.com
Subject: Re: [PATCH v1] regulator: core: Convert warning to debug print
Date: Thu, 12 Oct 2023 16:45:48 -0500	[thread overview]
Message-ID: <4ecd19e5-9dfa-4157-9384-92c722064b2e@linux.ibm.com> (raw)
In-Reply-To: <aa596890-d98a-41c2-bc10-8c1db58ea23a@sirena.org.uk>

Hello Mark,

Thanks for the review.

On 10/12/23 12:47, Mark Brown wrote:
> On Thu, Oct 12, 2023 at 12:42:35PM -0500, Ninad Palsule wrote:
>> 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
> This is a warning saying that the firmware description for the system is
> incomplete in case things go wrong later - it is vanishingly unlikely
> that these devices actually do not require supplies, we'd probably have
> heard about it if they did.  If a supply is not described properly we
> may for example decide to power off what we think is an unused supply
> with bad results.

You are right there are regulators for these supplies but they are 
managed by the
hardware hence not added in the device tree. I checked dts/aspeed 
directory and
non of the machine has “vcc-supply” defined and lot of them use eeprom.
Also, I thought that this message is only useful in the lab to indicate 
developer
whether they missed the device tree definition or not but its not useful 
in the
field.  Hence proposed to put it under DEBUG.

Please let me know if I missed something.

Thanks!

~ Ninad



  reply	other threads:[~2023-10-12 22:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-12 17:42 Ninad Palsule
2023-10-12 17:47 ` Mark Brown
2023-10-12 21:45   ` Ninad Palsule [this message]
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=4ecd19e5-9dfa-4157-9384-92c722064b2e@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