public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Laxman Dewangan <ldewangan@nvidia.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: "broonie@opensource.wolfsonmicro.com" 
	<broonie@opensource.wolfsonmicro.com>,
	"sameo@linux.intel.com" <sameo@linux.intel.com>,
	"lrg@ti.com" <lrg@ti.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V2] regulator: tps6586x: register regulator even if no init data
Date: Thu, 6 Sep 2012 17:01:01 +0530	[thread overview]
Message-ID: <50488975.2000009@nvidia.com> (raw)
In-Reply-To: <504770AD.8060103@wwwdotorg.org>

On Wednesday 05 September 2012 09:03 PM, Stephen Warren wrote:
> On 09/05/2012 02:02 AM, Laxman Dewangan wrote:
>> On Wednesday 05 September 2012 02:17 AM, Stephen Warren wrote:
>>> On 08/29/2012 09:01 AM, Laxman Dewangan wrote:
>>>> Register all TPS6586x regulators even if there is no regulator
>>>> init data for platform i.e. without any user-supplied constraints.
>>>>
>>>> Signed-off-by: Laxman Dewangan<ldewangan@nvidia.com>
>>> Tested-by: Stephen Warren<swarren@nvidia.com>
>>>
>>> Note that this patch depends on the patch I just posted titled
>>> "regulator: tps6586x: add support for SYS rail". I also believe Laxman
>>> will be posting another patch based on these 2 soon (it will move the
>>> regulator DT parsing out of the MFD driver into the regulator driver),
>>> so I guess it makes sense to take them all through the same TPS6586x
>>> topic branch in the regulator tree.
>> About next patch (moving regulator dt parsing out of mfd), do you want
>> to support the Harmony also?
>> If yes then same change should also contain the board-harmony-power.c
>> changes.
> Yes, Harmony needs to continue working.
>
> We can either:
>
> a) Add your third patch to the TPS6586x topic branch in the regulator
> tree, and I'll merge all 3 into the Tegra tree in order to build on it
> and switch the regulators to DT.
>
> b) You can wait to submit your third patch until after the 3.7 merge
> window (i.e. send if for 3.8) since then all the dependencies will have
> appeared in Linus's tree as a baseline. This is probably the simplest.

I will go with option (b) as this is just enhancement and not any 
critical bug fixes.


      reply	other threads:[~2012-09-06 11:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-29 15:01 [PATCH V2] regulator: tps6586x: register regulator even if no init data Laxman Dewangan
2012-08-29 17:38 ` Stephen Warren
2012-09-04 20:47 ` Stephen Warren
2012-09-05  8:02   ` Laxman Dewangan
2012-09-05 15:33     ` Stephen Warren
2012-09-06 11:31       ` Laxman Dewangan [this message]

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=50488975.2000009@nvidia.com \
    --to=ldewangan@nvidia.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrg@ti.com \
    --cc=sameo@linux.intel.com \
    --cc=swarren@wwwdotorg.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