From: MyungJoo Ham <myungjoo.ham@samsung.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: "Lukasz Majewski" <l.majewski@samsung.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Samuel Ortiz" <sameo@linux.intel.com>,
"Liam Girdwood" <lrg@slimlogic.co.uk>,
"Alessandro Zummo" <a.zummo@towertech.it>,
박경민 <kyungmin.park@samsung.com>, 심준영 <jy0922.shim@samsung.com>,
"myungjoo.ham@gmail.com" <myungjoo.ham@gmail.com>
Subject: Re: Re: [PATCH v4 2/3] regulator MAX8998/LP3974: Support DVS-GPIO.
Date: Wed, 05 Jan 2011 00:54:25 +0000 (GMT) [thread overview]
Message-ID: <24564862.361211294188865120.JavaMail.weblogic@epml11> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=euc-kr, Size: 1109 bytes --]
On Tue, Jan 04, 2011 at 22:44PM +0900, Mark Brown wrote:
> On Tue, Jan 04, 2011 at 05:16:56PM +0900, MyungJoo Ham wrote:
> > On Tue, Jan 4, 2011 at 4:49 PM, Lukasz Majewski wrote:
>
> > > Is it desirable to define all four for BUCK1 and two for BUCK2 DVS
> > > voltages in platform code?
>
> > In case a system with 4 buck1 preset voltages and 2 buck2 preset
> > voltages, it is desirable. :)
>
> I suspect Lukasz's question is more why this would be useful; I can
> imagine that the main reason would be performance and in any case I
> don't see it hurting to have the option.
>
Yes, it is supposed to be faster to set GPIO pins rather than sending values thru I2C busses. And some boards require all the four BUCK1 voltages and two BUCK2 voltages; e.g., S5PC110-Universal.
MyungJoo Ham (ÇÔ¸íÁÖ)
Mobile Software Platform Lab,
Digital Media and Communications (DMC) Business
Samsung Electronics
cell: +82-10-6714-2858 / office: +82-31-279-8033ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next reply other threads:[~2011-01-05 0:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-05 0:54 MyungJoo Ham [this message]
2011-01-05 11:26 ` Mark Brown
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=24564862.361211294188865120.JavaMail.weblogic@epml11 \
--to=myungjoo.ham@samsung.com \
--cc=a.zummo@towertech.it \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=jy0922.shim@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=l.majewski@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=myungjoo.ham@gmail.com \
--cc=sameo@linux.intel.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
Powered by JetHome