All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Regulator enable/disable delay based on board design: How to handle?
Date: Mon, 13 Feb 2012 08:37:12 -0800	[thread overview]
Message-ID: <20120213163711.GD3494@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4F38D55A.5020208@nvidia.com>

[-- Attachment #1: Type: text/plain, Size: 834 bytes --]

On Mon, Feb 13, 2012 at 02:48:18PM +0530, Laxman Dewangan wrote:

> We observed that some of the rail enable/disable settling time
> depends on the board design specially based on external capacitor
> connected on
> rails.  This is observed mainly on VBUS regulator rail where
> difference on the capacitance value which is connected on rail makes
> the on/off
> time to vary.

Usually this would be handled via regulator driver platform data as the
regulator will typically be designed with particular external components
in mind and (especially in the case of DCDC convertors) may need to be
configured differently depending on the choice of passive components.
Many regulators also have some software control for the ramp rate,
mainly intended to limit inrush currents on system startup, which can be
varied at runtime if desired.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-02-13 16:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-13  9:18 Regulator enable/disable delay based on board design: How to handle? Laxman Dewangan
2012-02-13 16:37 ` Mark Brown [this message]
2012-02-13 17:58   ` Laxman Dewangan
2012-02-14  1:09     ` Mark Brown
2012-02-14 11:23       ` Laxman Dewangan

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=20120213163711.GD3494@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=ldewangan@nvidia.com \
    --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.