public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@ti.com>
To: Lesly A M <leslyam@ti.com>
Cc: linux-omap@vger.kernel.org, Nishanth Menon <nm@ti.com>,
	David Derrick <dderrick@ti.com>,
	Samuel Ortiz <sameo@linux.intel.com>
Subject: Re: [PATCH 3/8] omap3: pm: Correcting the sys_offmode signal polarity
Date: Tue, 01 Mar 2011 14:35:04 -0800	[thread overview]
Message-ID: <87k4gifp0n.fsf@ti.com> (raw)
In-Reply-To: <1298723139-1693-4-git-send-email-leslyam@ti.com> (Lesly A. M.'s message of "Sat, 26 Feb 2011 17:55:34 +0530")

Lesly A M <leslyam@ti.com> writes:

> Changing the polarity of the sys_offmode signal to active low,
> to get a High to Low transition on the NSLEEP1 of PM IC when OMAP is
> entering offmode. Because on PM IC the power resources (LDO, DCDC regulators)
> associated with P1 group which is controlled by NSLEEP1 are set to sleep,
> when there is transition form High to Low.
>
> Signed-off-by: Lesly A M <leslyam@ti.com>
> Cc: Nishanth Menon <nm@ti.com>
> Cc: David Derrick <dderrick@ti.com>
> Cc: Samuel Ortiz <sameo@linux.intel.com>
> ---
>  arch/arm/mach-omap2/pm34xx.c |    4 ++++
>  1 files changed, 4 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/pm34xx.c b/arch/arm/mach-omap2/pm34xx.c
> index e46f4b5..8a7c756 100644
> --- a/arch/arm/mach-omap2/pm34xx.c
> +++ b/arch/arm/mach-omap2/pm34xx.c
> @@ -1034,6 +1034,10 @@ static int __init omap3_pm_init(void)
>  
>  	printk(KERN_ERR "Power Management for TI OMAP3.\n");
>  
> +	/* Changing the polarity of the sys_offmode signal to active low */
> +	omap2_prm_clear_mod_reg_bits(OMAP3430_OFFMODE_POL_MASK,
> +			OMAP3430_GR_MOD, OMAP3_PRM_POLCTRL_OFFSET);
> +

This change belongs in voltage code.

Kevin
>  	/* XXX prcm_setup_regs needs to be before enabling hw
>  	 * supervised mode for powerdomains */
>  	prcm_setup_regs();

  reply	other threads:[~2011-03-01 22:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-26 12:25 [PATCH v7 0/8] omap3: pm: TWL4030 power scripts and workaround for TWL errata 27 Lesly A M
2011-02-26 12:25 ` [PATCH 1/8] omap3: pm: Fix for the TRITON sleep/wakeup sequence Lesly A M
2011-03-01 22:33   ` Kevin Hilman
2011-03-02  6:08     ` Manuel, Lesly Arackal
2011-02-26 12:25 ` [PATCH 2/8] omap3: pm: Correct the warning print during script loading Lesly A M
2011-02-26 12:25 ` [PATCH 3/8] omap3: pm: Correcting the sys_offmode signal polarity Lesly A M
2011-03-01 22:35   ` Kevin Hilman [this message]
2011-03-02  6:11     ` Manuel, Lesly Arackal
2011-02-26 12:25 ` [PATCH 4/8] omap3: pm: TWL4030 power scripts for OMAP3 boards Lesly A M
2011-02-26 12:25 ` [PATCH 5/8] omap3: pm: TWL5030 version checking Lesly A M
2011-02-28  7:24   ` Krishnamoorthy, Balaji T
2011-02-28 11:04     ` Manuel, Lesly Arackal
2011-02-28 11:24       ` Krishnamoorthy, Balaji T
2011-02-26 12:25 ` [PATCH 6/8] mfd: TWL4030: changes for TRITON Errata 27 workaround Lesly A M
2011-02-26 12:25 ` [PATCH 7/8] omap3430: Updating the board file to use TWL4030 scripts Lesly A M
2011-02-26 12:25 ` [PATCH 8/8] omap3630: " Lesly A M
2011-03-01 22:31 ` [PATCH v7 0/8] omap3: pm: TWL4030 power scripts and workaround for TWL errata 27 Kevin Hilman
2011-03-02  5:57   ` Manuel, Lesly Arackal

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=87k4gifp0n.fsf@ti.com \
    --to=khilman@ti.com \
    --cc=dderrick@ti.com \
    --cc=leslyam@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=nm@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