From: Guenter Roeck <linux@roeck-us.net>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org, linaro-kernel@lists.linaro.org,
atull@opensource.altera.com
Subject: Re: [PATCH] regulator: of: Lower the severity of the error with no container
Date: Wed, 8 Oct 2014 15:59:12 -0700 [thread overview]
Message-ID: <20141008225912.GA25134@roeck-us.net> (raw)
In-Reply-To: <20141008223601.GP4609@sirena.org.uk>
On Wed, Oct 08, 2014 at 11:36:01PM +0100, Mark Brown wrote:
> On Wed, Oct 08, 2014 at 03:34:03PM -0700, Guenter Roeck wrote:
>
> > Would it also be possible to lower the severity of the "no parameters"
> > message ?
>
> Could you be more specific please?
There is a log message "no parameters" for each regulator. This is printed
unconditionally from print_constraints().
Looking through the code again, looks like this is on purpose. It is just a bit
annoying to get lots of those messages. One of the systems I am dealing with has
17 LTC2978 chips in it, with 8 channels each. That results in 136 times "no
parameters" in the boot log. And that is not even a fully populated system;
if fully populated, there can be more than 60 of those chips. 500+ lines of
similar log messages is really a bit on the high side.
It might help if there was a way to silence the messages, ie to make
"print_constraints" optional.
Thanks,
Guenter
next prev parent reply other threads:[~2014-10-08 22:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 22:09 [PATCH] regulator: of: Lower the severity of the error with no container Mark Brown
2014-10-08 22:34 ` Guenter Roeck
2014-10-08 22:36 ` Mark Brown
2014-10-08 22:59 ` Guenter Roeck [this message]
2014-10-08 23:45 ` Mark Brown
2014-10-09 0:05 ` Guenter Roeck
2014-10-09 0:12 ` Mark Brown
2014-10-09 0:25 ` Guenter Roeck
2014-10-09 15:54 ` Mark Brown
2014-10-09 16:14 ` Guenter Roeck
2014-10-09 17:49 ` Guenter Roeck
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=20141008225912.GA25134@roeck-us.net \
--to=linux@roeck-us.net \
--cc=atull@opensource.altera.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linaro-kernel@lists.linaro.org \
--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.