linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] regulator: Add ramp_delay to regulator constraints to get used as a configurable parameter.
Date: Sun, 17 Jun 2012 21:14:19 +0100	[thread overview]
Message-ID: <20120617201419.GU4267@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1339416668-17028-1-git-send-email-yadi.brar@samsung.com>

On Mon, Jun 11, 2012 at 05:41:08PM +0530, Yadwinder Singh Brar wrote:
> For some hardwares ramp_delay for BUCKs is a configurable parameter which can
> be configured through DT or board file.This patch adds ramp_delay to regulator
> constraints and allow user to configure it for regulators which supports this
> feature, through DT or board file. It will provide two ways of setting the
> ramp_delay for a regulator:

Applied, thanks - sorry about the delay, you submitted the day before I
flew back from China.  I rewrote the subject line to fit in 80 columns,
otherwise things like git log and pull requests look odd.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120617/7d19f02e/attachment.sig>

      reply	other threads:[~2012-06-17 20:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-11 12:11 [PATCH] regulator: Add ramp_delay to regulator constraints to get used as a configurable parameter Yadwinder Singh Brar
2012-06-17 20:14 ` Mark Brown [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=20120617201419.GU4267@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).