public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthias Kaehlcke <mka@chromium.org>
To: "H. Nikolaus Schaller" <hns@goldelico.com>
Cc: linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>,
	letux-kernel@openphoenux.org
Subject: Re: [PATCH] regulator: core: silence warning: "VDD1: ramp_delay not set"
Date: Thu, 27 Oct 2016 10:41:09 -0700	[thread overview]
Message-ID: <20161027174109.GA185131@google.com> (raw)
In-Reply-To: <625675256c0d75805f088b4be17a3308dc1b7ea4.1477571498.git.hns@goldelico.com>

El Thu, Oct 27, 2016 at 02:31:39PM +0200 H. Nikolaus Schaller ha dit:

> commit 73e705bf81ce ("regulator: core: Add set_voltage_time op")
> 
> introduced a new rdev_warn() if the ramp_delay is 0.
> 
> Apparently, on omap3/twl4030 platforms with dynamic voltage
> management this results in non-ending spurious messages like
> 
> [  511.143066] VDD1: ramp_delay not set
> [  511.662322] VDD1: ramp_delay not set
> [  513.903625] VDD1: ramp_delay not set
> [  514.222198] VDD1: ramp_delay not set
> [  517.062835] VDD1: ramp_delay not set
> [  517.382568] VDD1: ramp_delay not set
> [  520.142791] VDD1: ramp_delay not set
> [  520.502593] VDD1: ramp_delay not set
> [  523.062896] VDD1: ramp_delay not set
> [  523.362701] VDD1: ramp_delay not set
> [  526.143035] VDD1: ramp_delay not set
> 
> I have observed this on GTA04 while it is reported to occur on
> N900 as well: https://bugzilla.kernel.org/show_bug.cgi?id=178371
> 
> This patch makes the warning appear only in debugging mode.
> 
> Signed-off-by: H. Nikolaus Schaller <hns@goldelico.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 67426c0..5c1519b 100644
> --- a/drivers/regulator/core.c
> +++ b/drivers/regulator/core.c
> @@ -2754,7 +2754,7 @@ static int _regulator_set_voltage_time(struct regulator_dev *rdev,
>  		ramp_delay = rdev->desc->ramp_delay;
>  
>  	if (ramp_delay == 0) {
> -		rdev_warn(rdev, "ramp_delay not set\n");
> +		rdev_dbg(rdev, "ramp_delay not set\n");
>  		return 0;
>  	}

Sorry about that, I didn't run into this since in my tests ramp_delay
was set :(

Calling _regulator_set_voltage_time() with ramp_delay being zero is
a common case, I think the message should be removed completely.

Thanks

Matthias

  reply	other threads:[~2016-10-27 17:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-27 12:31 [PATCH] regulator: core: silence warning: "VDD1: ramp_delay not set" H. Nikolaus Schaller
2016-10-27 17:41 ` Matthias Kaehlcke [this message]
2016-10-27 17:45   ` H. Nikolaus Schaller
2016-10-27 18:06     ` Matthias Kaehlcke

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=20161027174109.GA185131@google.com \
    --to=mka@chromium.org \
    --cc=broonie@kernel.org \
    --cc=hns@goldelico.com \
    --cc=letux-kernel@openphoenux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox