public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Saravana Kannan <skannan@codeaurora.org>
Cc: linux-arm-msm@vger.kernel.org,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regulator: Call into regulator driver only when voltage min/max really changes.
Date: Mon, 13 Dec 2010 14:41:10 +0000	[thread overview]
Message-ID: <1292251270.3320.79.camel@odin> (raw)
In-Reply-To: <1292151342-12970-1-git-send-email-skannan@codeaurora.org>

On Sun, 2010-12-12 at 02:55 -0800, Saravana Kannan wrote:
> Even in cases where the consumer driver calls the regulator core with
> different voltage min/max values, the application of the various
> voltage constraints could result in the min/max voltage values passed
> to the regulator driver to be unchanged since the previous invocation.
> 
> Optimize these cases by not calling into the regulator driver and not
> sending incorrect/unnecessary voltage change notifications.
> 
> Signed-off-by: Saravana Kannan <skannan@codeaurora.org>

This doesn't apply. Any chance you could regenerate against the
regulator for-next branch ?

Thanks

Liam  
-- 
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk


      parent reply	other threads:[~2010-12-13 14:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-12 10:55 [PATCH] regulator: Call into regulator driver only when voltage min/max really changes Saravana Kannan
2010-12-12 12:18 ` Mark Brown
2010-12-12 12:41   ` skannan
2010-12-12 13:13     ` Mark Brown
2010-12-12 13:53 ` Mark Brown
2010-12-12 21:41   ` Saravana Kannan
2010-12-13 14:41 ` 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=1292251270.3320.79.camel@odin \
    --to=lrg@slimlogic.co.uk \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=skannan@codeaurora.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