All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@ti.com>
To: Tero Kristo <t-kristo@ti.com>
Cc: linux-omap@vger.kernel.org, Nishanth Menon <nm@ti.com>
Subject: Re: [PATCHv3 05/11] OMAP2+: PM: provide mechanism to describe overall behavior of osc and PMIC.
Date: Fri, 04 Nov 2011 14:02:24 -0700	[thread overview]
Message-ID: <87d3d78uu7.fsf@ti.com> (raw)
In-Reply-To: <1317835031-8201-6-git-send-email-t-kristo@ti.com> (Tero Kristo's message of "Wed, 5 Oct 2011 20:17:05 +0300")

Tero Kristo <t-kristo@ti.com> writes:

> From: Nishanth Menon <nm@ti.com>
>
> We currently have mechanisms in place to describe the PMIC per
> rail, however we also need to configure the system for situations
> such as OFF mode, where, oscillator switch off and on time, and
> similar durations for PMIC also tends to play a major factor.
> Introduce a few apis to OMAP2's pm framework to use these. OMAP1
> does'nt seem to need this at the moment, hence not a OMAP generic
> framework. The set functions are meant to be used by initialization
> code.
>
> The OMAP specific implementation would need to use this ofcourse.
>
> Signed-off-by: Nishanth Menon <nm@ti.com>

> ---
>  arch/arm/mach-omap2/pm.c |  122 ++++++++++++++++++++++++++++++++++++++++++++++
>  arch/arm/mach-omap2/pm.h |   18 +++++++
>  2 files changed, 140 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/pm.c b/arch/arm/mach-omap2/pm.c
> index 659e400..e130d92 100644
> --- a/arch/arm/mach-omap2/pm.c
> +++ b/arch/arm/mach-omap2/pm.c
> @@ -24,6 +24,52 @@
>  #include "clockdomain.h"
>  #include "pm.h"
>  
> +/**
> + * struct omap2_pm_lp_description - Describe low power behavior of the system
> + * @oscillator_startup_time:	Time rounded up to uSec for the oscillator to
> + *				provide a stable clock from power on.
> + * @oscillator_shutdown_time:	Time rounded up to uSec for oscillator to safely
> + *				switch off.
> + * @pmic_startup_time:		Time rounded up to uSec for the PMIC to
> + *				provide be ready for operation from low power
> + *				state. Note: this is not the same as voltage
> + *				rampup time, instead, consider the PMIC to be
> + *				in lowest power state(say OFF), this is the time
> + *				required for it to become ready for it's DCDCs
> + *				or LDOs to start operation.
> + * @pmic_shutdown_time:		Time rounded up to uSec for the PMIC to
> + *				go to low power after the LDOs are pulled to
> + *				appropriate state. Note: this is not the same as
> + *				voltage rampdown time, instead, consider the
> + *				PMIC to have switched it's LDOs down, this is
> + *				time taken to reach it's lowest power state(say
> + *				sleep/OFF).

IMO, These PMIC times should be part of the existing struct that
describes all the configurable PMIC settings.

Kevin

  reply	other threads:[~2011-11-04 21:02 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-05 17:17 [PATCHv3 00/11] voltage domain cleanup Tero Kristo
2011-10-05 17:17 ` [PATCHv3 01/11] OMAP3+: PM: VP: use uV for max and min voltage limits Tero Kristo
2011-10-05 17:17 ` [PATCHv3 02/11] omap: voltage: add definitions for omap_vp_param and omap_vc_param Tero Kristo
2011-10-05 17:17 ` [PATCHv3 03/11] omap3: add vp and vc parameter data Tero Kristo
2011-11-04 20:22   ` Kevin Hilman
2011-10-05 17:17 ` [PATCHv3 04/11] omap4: " Tero Kristo
2011-11-04 20:22   ` Kevin Hilman
2011-10-05 17:17 ` [PATCHv3 05/11] OMAP2+: PM: provide mechanism to describe overall behavior of osc and PMIC Tero Kristo
2011-11-04 21:02   ` Kevin Hilman [this message]
2011-10-05 17:17 ` [PATCHv3 06/11] omap3+: vc: use new vc_params and vp_params in parameter calculations Tero Kristo
2011-11-04 21:11   ` Kevin Hilman
2011-10-05 17:17 ` [PATCHv3 07/11] omap3+: vp: use new vp_params for calculating vddmin and vddmax Tero Kristo
2011-11-04 21:13   ` Kevin Hilman
2011-10-05 17:17 ` [PATCHv3 08/11] omap3+: voltage: remove obsolete parameters Tero Kristo
2011-11-04 21:17   ` Kevin Hilman
2011-10-05 17:17 ` [PATCHv3 09/11] omap4: twl: added pmic startup / shutdown times Tero Kristo
2011-11-04 21:21   ` Kevin Hilman
2011-11-04 21:21   ` Kevin Hilman
2011-10-05 17:17 ` [PATCHv3 10/11] omap3+: use lp params for calculating clock setup times Tero Kristo
2011-11-04 21:38   ` Kevin Hilman
2011-11-15 17:22     ` Tero Kristo
2011-11-17  0:10       ` Kevin Hilman
2011-10-05 17:17 ` [PATCHv3 11/11] omap4: use lp params for calculating pmic " Tero Kristo
2011-11-04 20:49   ` Kevin Hilman

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=87d3d78uu7.fsf@ti.com \
    --to=khilman@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=t-kristo@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.