From: Kukjin Kim <kgene.kim@samsung.com>
To: "'Kukjin Kim'" <kgene.kim@samsung.com>,
kyungmin.park@samsung.com, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org
Cc: lrg@slimlogic.co.uk, "'Changhwan Youn'" <chaos.youn@samsung.com>,
"'MyungJoo Ham'" <myungjoo.ham@samsung.com>,
"'Mark Brown'" <broonie@opensource.wolfsonmicro.com>
Subject: RE: [PATCH v3] regulators: add support max8952 regulator
Date: Tue, 28 Sep 2010 16:58:49 +0900 [thread overview]
Message-ID: <006201cb5ee3$0100fc20$0302f460$%kim@samsung.com> (raw)
In-Reply-To:
Kukjin Kim wrote:
>
> Kyungmin Park wrote:
> >
> > Do you check the DVS feature?
> > It can support the DVS by GPIOs and platform can set the each voltages
at
> > each mode.
> >
> Ok...I agree about the feature's necessity that you said.
>
> However, we don't need separate driver which has same/similar
functionality.
> So...would be better that could implement it in max8649...
>
> Could you please do it based on this?...in fact, can't test it on SMDK.
>
Hmm...
Kyungmin, if you have no time to do it, my team will do it.
Is it ok?
> Thanks.
>
> Best regards,
> Kgene.
> --
> Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
> SW Solution Development Team, Samsung Electronics Co., Ltd.
>
> > As quick review of max8649. It can't support it.
> >
> > Thank you,
> > Kyungmin Park
> >
> > -----Original Message-----
> > From: Kukjin Kim [mailto:kgene.kim@samsung.com]
> > Sent: Wednesday, September 08, 2010 8:26 AM
> > To: linux-kernel@vger.kernel.org; linux-arm-kernel@lists.infradead.org;
> > linux-samsung-soc@vger.kernel.org
> > Cc: lrg@slimlogic.co.uk; Changhwan Youn; Kukjin Kim; MyungJoo Ham;
> Kyungmin
> > Park
> > Subject: [PATCH v3] regulators: add support max8952 regulator
> >
> > From: Changhwan Youn <chaos.youn@samsung.com>
> >
> > The operation of max8952 is almost similar to max8649 except the output
> > voltage range. This patch adds support the max8952 regulator using
> > current max8649 implementation. And removes separate max8952.[ch] files
> > since the functionality is now merged into this driver.
> >
> > Signed-off-by: Changhwan Youn <chaos.youn@samsung.com>
> > Signed-off-by: Kukjin Kim <kgene.kim@samsung.com>
> > Cc: MyungJoo Ham <myungjoo.ham@samsung.com>
> > Cc: Kyungmin Park <kyungmin.park@samsung.com>
> > Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> > ---
> > Following is as per Mark Brown's suggestion.
> > Changes since v2:
> > - Removed separate max8952.[ch] files
> >
> > Changes since v1:
> > - Added returning fail when detected wrong ID
> > - Added matching the ID from the chip in case the user got things wrong
> > - Added enum chip ID instead of 0, 1
> >
> (snip)
next prev parent reply other threads:[~2010-09-28 7:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 23:26 Kukjin Kim
2010-09-08 2:56 ` Kyungmin Park
2010-09-08 12:28 ` Kukjin Kim
2010-09-28 7:58 ` Kukjin Kim [this message]
2010-09-28 8:03 ` Kyungmin Park
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='006201cb5ee3$0100fc20$0302f460$%kim@samsung.com' \
--to=kgene.kim@samsung.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=chaos.youn@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=myungjoo.ham@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®