linux-tegra.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
To: Laxman Dewangan <ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: "lrg-l0cyMroinI0@public.gmane.org"
	<lrg-l0cyMroinI0@public.gmane.org>,
	"jedu-kDsPt+C1G03kYMGBc/C6ZA@public.gmane.org"
	<jedu-kDsPt+C1G03kYMGBc/C6ZA@public.gmane.org>,
	"sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.org"
	<sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>,
	"gg-kDsPt+C1G03kYMGBc/C6ZA@public.gmane.org"
	<gg-kDsPt+C1G03kYMGBc/C6ZA@public.gmane.org>,
	"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH V1] regulator: tps65910: Sleep control through external inputs
Date: Tue, 24 Jan 2012 21:21:44 +0000	[thread overview]
Message-ID: <20120124212144.GG1135@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4F1EA608.3020204-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1028 bytes --]

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.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2012-01-24 21:21 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 [this message]
2012-01-25  6:22                     ` Laxman Dewangan

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=20120124212144.GG1135@opensource.wolfsonmicro.com \
    --to=broonie-yzvpicuk2aatku/dhu1wvuem+bqzidxxqq4iyu8u01e@public.gmane.org \
    --cc=gg-kDsPt+C1G03kYMGBc/C6ZA@public.gmane.org \
    --cc=jedu-kDsPt+C1G03kYMGBc/C6ZA@public.gmane.org \
    --cc=ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=lrg-l0cyMroinI0@public.gmane.org \
    --cc=sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).