linux-tegra.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laxman Dewangan <ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: Mark Brown
	<broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@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 18:07:28 +0530	[thread overview]
Message-ID: <4F1EA608.3020204@nvidia.com> (raw)
In-Reply-To: <20120124122411.GB31839-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>

On Tuesday 24 January 2012 05:54 PM, Mark Brown wrote:
> On Tue, Jan 24, 2012 at 05:49:52PM +0530, Laxman Dewangan wrote:
> The external controls for different rails are managed by power
>> manament driver of soc in kernel to toggel them. The bootloader make
>> sure that all external control signals are active just before
>> jumping into kernel so that there is no issue during regulator init.
>> When system reboots in kernel by kernel command, the configuration
>> of the pmu still maintain as what it was in kernel before reboot and
>> issue  system reboots. There is possibility that the default (POR)
>> of these control signals are not active on soc reset or initial
>> stage of the bootloader and hence it can turn off the rails which
>> can avoid system booting.
>> So kernel need to remove all external controls before reboot system.
> The code needs to explain this stuff so readers will know.
>
Will add this information in code.
>
>> Hmm.., I thought that  suspend mode apis manages the low/full-on
>> power mode when the controls are not through external inputs. There
>> is different register for configuring the power mode by i2c- write.
>> This macro help in configuration of mode when enabled with external
>> controls which configures in different sets of register.
> No, usually it's used for configuring suspend mode when the PMIC knows
> about system suspend.
>
Ok, will move this configuration with the  suspend mode and program the 
correct register based on external signals.

> I used this member in the probe as for configuring the rails..
>> +        err = tps65910_set_ext_sleep_config(pmic, i,
>> +                pmic_plat_data->regulator_ext_sleep_control[i]);
> Right, but I can't see any code which manages the signals at runtime.
> You tell the device to use the signals but the signals aren't (as far as
> I can see) controlled by software.
I dont think we need to supply information that how EN1/EN2/EN3 toggles 
from external word?
This should be done on the consumer driver  for these rails to toggle 
the signals based on requirements.

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.




> --
> To unsubscribe from this list: send the line "unsubscribe linux-tegra" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2012-01-24 12:37 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 [this message]
     [not found]                 ` <4F1EA608.3020204-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-01-24 21:21                   ` Mark Brown
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=4F1EA608.3020204@nvidia.com \
    --to=ldewangan-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
    --cc=broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org \
    --cc=gg-kDsPt+C1G03kYMGBc/C6ZA@public.gmane.org \
    --cc=jedu-kDsPt+C1G03kYMGBc/C6ZA@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).