From: Mark Brown <broonie@kernel.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Chanwoo Choi <cw00.choi@samsung.com>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"sbkim73@samsung.com" <sbkim73@samsung.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Kyungmin Park <kyungmin.park@samsung.com>
Subject: Re: [PATCH 1/2] regulator: s5m8767: Modify parse_dt function to parse data related to ramp
Date: Thu, 10 Oct 2013 18:36:27 +0100 [thread overview]
Message-ID: <20131010173627.GR21581@sirena.org.uk> (raw)
In-Reply-To: <20131010165100.GA3910@e106331-lin.cambridge.arm.com>
[-- Attachment #1: Type: text/plain, Size: 543 bytes --]
On Thu, Oct 10, 2013 at 05:51:00PM +0100, Mark Rutland wrote:
> On Thu, Oct 10, 2013 at 12:10:53PM +0100, Chanwoo Choi wrote:
> > Turn on ramp control of buck2/3/4.
> Ok, but why does this need to be in the dt?
Ramp control is a hardware system integration decision which people
working with regulators should be familiar with - you're trading off
speed of power on or voltage change for maximum current draw from the
regulator supply. The term should be sufficiently clear to an engineer
who can make an informed decision about using it.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-10-10 17:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-10 1:41 Chanwoo Choi
2013-10-10 1:41 ` [PATCH 2/2] regulator: s5m8767: Modify parsing method of the voltage table of buck2/3/4 Chanwoo Choi
2013-10-10 10:36 ` Mark Rutland
2013-10-10 11:46 ` Chanwoo Choi
2013-10-10 10:28 ` [PATCH 1/2] regulator: s5m8767: Modify parse_dt function to parse data related to ramp Mark Rutland
2013-10-10 11:10 ` Chanwoo Choi
2013-10-10 16:51 ` Mark Rutland
2013-10-10 17:36 ` Mark Brown [this message]
2013-10-24 10:15 ` Mark Brown
2013-10-25 9:08 ` Chanwoo Choi
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=20131010173627.GR21581@sirena.org.uk \
--to=broonie@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=sbkim73@samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®