All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Walmsley <paul@pwsan.com>
To: Benoit Cousson <b-cousson@ti.com>
Cc: rnayak@ti.com, linux-omap@vger.kernel.org,
	Santosh Shilimkar <santosh.shilimkar@ti.com>
Subject: Re: [PATCH 3/3] OMAP4: powerdomain data: Fix core mem states and missing cefuse flag
Date: Thu, 30 Jun 2011 17:48:29 -0600 (MDT)	[thread overview]
Message-ID: <alpine.DEB.2.00.1106301730340.2874@utopia.booyaka.com> (raw)
In-Reply-To: <1308847544-2322-4-git-send-email-b-cousson@ti.com>

On Thu, 23 Jun 2011, Benoit Cousson wrote:

> Since ES2.0, the core ocmram does not support a different state
> than the main power domain anymore during both ON and RET power
> domain state.
> Since PM is not supported at all in ES1.0, update the common
> structure.
> 
> LOWPOWERSTATECHANGE is supported by the cefuse power domain but
> the flag was missing.
> Add the PWRDM_HAS_LOWPOWERSTATECHANGE in flags field.
> 
> Indent all previous flags to be aligned with other fields.
> 
> Update the TI copyright date to 2011.
> 
> Signed-off-by: Benoit Cousson <b-cousson@ti.com>
> Cc: Paul Walmsley <paul@pwsan.com>
> Cc: Rajendra Nayak <rnayak@ti.com>
> Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>

Reviewed-by: Paul Walmsley <paul@pwsan.com>

I guess the CEFUSE LOWPOWERSTATECHANGE bit is in the Security TRM?


- Paul

  reply	other threads:[~2011-06-30 23:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-23 16:45 [PATCH 0/3] OMAP4: PRCM fixes Benoit Cousson
2011-06-23 16:45 ` [PATCH 1/3] OMAP4: pcrm: Fix errors in few defines name Benoit Cousson
2011-06-30 23:02   ` Paul Walmsley
2011-06-23 16:45 ` [PATCH 2/3] OMAP4: prm: Remove wrong clockdomain offsets Benoit Cousson
2011-06-30 23:12   ` Paul Walmsley
2011-06-23 16:45 ` [PATCH 3/3] OMAP4: powerdomain data: Fix core mem states and missing cefuse flag Benoit Cousson
2011-06-30 23:48   ` Paul Walmsley [this message]
2011-07-01 10:09     ` Cousson, Benoit
2011-06-30 23:55 ` [PATCH 0/3] OMAP4: PRCM fixes Paul Walmsley

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=alpine.DEB.2.00.1106301730340.2874@utopia.booyaka.com \
    --to=paul@pwsan.com \
    --cc=b-cousson@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=rnayak@ti.com \
    --cc=santosh.shilimkar@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.