From: Liam Girdwood <lrg@ti.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Jassi Brar <jaswinder.singh@linaro.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regulator: core: Optimise enable/disable path for always on regulators
Date: Thu, 19 Apr 2012 19:35:36 +0100 [thread overview]
Message-ID: <1334860536.4452.0.camel@odin> (raw)
In-Reply-To: <1334838618-27924-1-git-send-email-broonie@opensource.wolfsonmicro.com>
On Thu, 2012-04-19 at 13:30 +0100, Mark Brown wrote:
> If a regulator is always on for any reason then cache that when the
> consumer is created and use it to optimise away the need to take locks
> or recurse up the supply tree when consumers do enable or disable calls.
> The scheduling of asynchronous work for bulk enables is also skipped.
>
> We don't actually check if the device physically supports control on the
> basis that constraints allowing status changes on physically always on
> regulators are nonsensical anyway.
>
> This is a very common pattern in hardware - it's normal to have some
> power supplies that have either no software control or are critical to
> system function - so many systems should be able to benefit.
>
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> ---
Acked-by: Liam Girdwood <lrg@ti.com>
prev parent reply other threads:[~2012-04-19 18:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 12:30 [PATCH] regulator: core: Optimise enable/disable path for always on regulators Mark Brown
2012-04-19 18:35 ` 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=1334860536.4452.0.camel@odin \
--to=lrg@ti.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=jaswinder.singh@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.