All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liam Girdwood <lrg@ti.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"patches@opensource.wolfsonmicro.com" 
	<patches@opensource.wolfsonmicro.com>,
	David Collins <collinsd@codeaurora.org>
Subject: Re: [PATCH] regulator: If we can't configure optimum mode we're always in the best one
Date: Mon, 16 May 2011 13:18:59 +0100	[thread overview]
Message-ID: <4DD11633.6020302@ti.com> (raw)
In-Reply-To: <1305397185-22024-1-git-send-email-broonie@opensource.wolfsonmicro.com>

On 14/05/11 19:19, Mark Brown wrote:
> If either a regulator driver can't tell us what the optimum mode is (or
> doesn't have modes in the first place) or the system doesn't allow DRMS
> changes then it's more helpful for users to just say that we're in the
> optimal mode, even if it's from a selection of one.
> 
> Still report errors if the process of picking and setting a mode changes as
> this may indicate that we're stuck in a low power mode and unable to deliver
> a higher current that the consumer just asked for.
> 
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> ---
>  drivers/regulator/core.c |   16 +++++++++++++---
>  1 files changed, 13 insertions(+), 3 deletions(-)
> 

Applied.

Thanks

Liam

      reply	other threads:[~2011-05-16 12:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-14 18:19 [PATCH] regulator: If we can't configure optimum mode we're always in the best one Mark Brown
2011-05-16 12:18 ` Liam Girdwood [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=4DD11633.6020302@ti.com \
    --to=lrg@ti.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=collinsd@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@opensource.wolfsonmicro.com \
    /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.