All of lore.kernel.org
 help / color / mirror / Atom feed
From: jonghwa3.lee@samsung.com
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lrg@ti.com>,
	linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
	Myungjoo Ham <myungjoo.ham@samsung.com>
Subject: Re: [PATCH] regulator: max77693: Add max77693 regualtor driver.
Date: Mon, 24 Jun 2013 10:54:26 +0900	[thread overview]
Message-ID: <51C7A6D2.8060709@samsung.com> (raw)
In-Reply-To: <20130621151930.GB27646@sirena.org.uk>

Hi,
On 2013년 06월 22일 00:19, Mark Brown wrote:

> On Thu, Jun 20, 2013 at 04:03:26PM +0900, Jonghwa Lee wrote:
>> This patch adds new regulator driver to support max77693 chip's regulators.
>> max77693 has two linear voltage regulators and one current regulator which
>> can be controlled through I2C bus. This driver also supports device tree.
> 
> This is fine but doesn't have a binding document which is needed for new
> DT bindings.
> 


I'd like to add binding document to max77693 mfd's but it is still in progress
(https://lkml.org/lkml/2013/4/9/221). I think I can updates it when the patch
is merged. Do you think I have to wait for merging? Or just add document under
regulator/ this time ,and then move it to mfd/ later? Which one do you think better?

> A comment in the is_enabled() function explaining that more than one bit
> might be set (or replacing it with the generic function) would also be
> good.


Yes, the charger regulator needs two bits for checking enabling. I'll add the
comment about it.

Thanks,
Jonghwa


  reply	other threads:[~2013-06-24  1:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-20  7:03 [PATCH] regulator: max77693: Add max77693 regualtor driver Jonghwa Lee
2013-06-21 15:19 ` Mark Brown
2013-06-24  1:54   ` jonghwa3.lee [this message]
2013-06-24 10:30     ` 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=51C7A6D2.8060709@samsung.com \
    --to=jonghwa3.lee@samsung.com \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=lrg@ti.com \
    --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 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.