linux-tegra.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laxman Dewangan <ldewangan@nvidia.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: "lrg@ti.com" <lrg@ti.com>,
	"jedu@slimlogic.co.uk" <jedu@slimlogic.co.uk>,
	"sameo@linux.intel.com" <sameo@linux.intel.com>,
	"gg@slimlogic.co.uk" <gg@slimlogic.co.uk>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH V1] regulator: tps65910: Sleep control through external inputs
Date: Wed, 25 Jan 2012 11:52:25 +0530	[thread overview]
Message-ID: <4F1F9FA1.4000000@nvidia.com> (raw)
In-Reply-To: <20120124212144.GG1135@opensource.wolfsonmicro.com>

On Wednesday 25 January 2012 02:51 AM, Mark Brown wrote:
> * PGP Signed by an unknown key
>
> On Tue, Jan 24, 2012 at 06:07:28PM +0530, Laxman Dewangan wrote:
>
>> E.g. If cpu power is in VDDCTRL rail and if DVFS mechanism of SOC
>> wants that cpu rails to be ON, it will make the control signal
>> active and if it wants to disable the rail then it will deactivate
>> it.
>> The toggling of the control lines depends on how the power
>> management controller is designed for a given SOC and how it
>> manages.
> Hrm, right.  This isn't something that the regulator API usually deals
> with - normally we just deal with things that Linux owns and assume that
> if the hardware is wired up for something else to own the regulator it
> will deal with that completely including the configuration.  If we do
> need to do something here we need to make sure that the normal regulator
> code doesn't try to do anything clever with the regulator which messes
> up the other device.  But I guess this doesn't really have a problem
> with that, someone can always add a further patch optionally specifying
> GPIOs which won't conflict with this approach.
Thanks, I will send patch v2 having all fixes which is discuss in patch V1.
> * Unknown Key
> * 0x6E30FDDD

      reply	other threads:[~2012-01-25  6:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-24  9:05 [PATCH V1] regulator: tps65910: Sleep control through external inputs Laxman Dewangan
     [not found] ` <1327395919-32378-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-01-24 11:58   ` Mark Brown
     [not found]     ` <20120124115855.GC14888-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-01-24 12:19       ` Laxman Dewangan
     [not found]         ` <4F1EA1E8.90104-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-01-24 12:24           ` Mark Brown
     [not found]             ` <20120124122411.GB31839-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-01-24 12:37               ` Laxman Dewangan
     [not found]                 ` <4F1EA608.3020204-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-01-24 21:21                   ` Mark Brown
2012-01-25  6:22                     ` 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=4F1F9FA1.4000000@nvidia.com \
    --to=ldewangan@nvidia.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=gg@slimlogic.co.uk \
    --cc=jedu@slimlogic.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=lrg@ti.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;
as well as URLs for NNTP newsgroup(s).