public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Laxman Dewangan <ldewangan@nvidia.com>
To: Mark Brown <broonie@kernel.org>
Cc: <lgirdwood@gmail.com>, <linux-kernel@vger.kernel.org>,
	<cfreeman@nvidia.com>, <abrestic@chromium.org>,
	<afrid@nvidia.com>
Subject: Re: [PATCH 1/2] regulator: core: add support to get VSEL register from hw driver
Date: Fri, 5 Jun 2015 19:06:35 +0530	[thread overview]
Message-ID: <5571A5E3.3070700@nvidia.com> (raw)
In-Reply-To: <20150529094941.GL21577@sirena.org.uk>


On Friday 29 May 2015 03:19 PM, Mark Brown wrote:
> The problem will be there when external controller use the DVS pin for DVFS
> and need two register address here. In this case, I think external
> controller need to get information from different mechanism rather than via
> regulator driver to avoid complication on regulator driver/framework.
> Probably, it's definitely getting complicated (though in this case where
> we only need one register we ought to be more able to manage it, not
> that I have bright ideas right now).
>
Hi Mark,
Are you accepting this patch? I am not much clear on the conclusion and 
hence my question is.

Is anything pending  from me to provide any information?

I have some more patches pending on MAX8973 for supporting MAX77621 
device and if this series is not fine, I like to go on next set of 
patches while we discussing this need.

Thanks,
Laxman


  parent reply	other threads:[~2015-06-05 13:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-27 14:40 [PATCH 1/2] regulator: core: add support to get VSEL register from hw driver Laxman Dewangan
2015-05-27 14:40 ` [PATCH 2/2] regulator: max8973: Implement callback to get vsel and mask Laxman Dewangan
2015-05-28 13:52 ` [PATCH 1/2] regulator: core: add support to get VSEL register from hw driver Mark Brown
2015-05-29  5:51   ` Laxman Dewangan
2015-05-29  9:49     ` Mark Brown
2015-05-29 11:43       ` Laxman Dewangan
2015-06-05 13:36       ` Laxman Dewangan [this message]
2015-06-05 16:58         ` 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=5571A5E3.3070700@nvidia.com \
    --to=ldewangan@nvidia.com \
    --cc=abrestic@chromium.org \
    --cc=afrid@nvidia.com \
    --cc=broonie@kernel.org \
    --cc=cfreeman@nvidia.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.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