All of lore.kernel.org
 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: Mon, 16 Oct 2023 07:24:59 -0500	[thread overview]
Message-ID: <df9cffef-ef00-4e52-9df1-8bed3605a014@linux.ibm.com> (raw)
In-Reply-To: <ZSlkWZvtEFfSkqNE@finisterre.sirena.org.uk>

Hello Mark,

On 10/13/23 10:38, Mark Brown wrote:
> On Thu, Oct 12, 2023 at 04:45:48PM -0500, Ninad Palsule wrote:
>
>> 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.
> Fixed voltage regulators can be used for this.
ok, So far we don't need it.
>
>> 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.
> The theory is that it shouldn't come up in the field since people see it
> during development and fix things then, are people actually looking at
> these logs?  I think my understanding was that they're mostly BMCs
> people interacted with via a UI of some kind.

During testing people look at this logs. We will ignore this warning for 
now.

Thanks!

~Ninad


      reply	other threads:[~2023-10-16 12:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-12 17:42 [PATCH v1] regulator: core: Convert warning to debug print Ninad Palsule
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 [this message]

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=df9cffef-ef00-4e52-9df1-8bed3605a014@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.