All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: Mike Turquette <mturquette@ti.com>
Cc: Lesly AM <x0080970@ti.com>, Mike Rapoport <mike@compulab.co.il>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"Menon, Nishanth" <nm@ti.com>, "Derrick, David" <dderrick@ti.com>,
	Samuel Ortiz <sameo@linux.intel.com>
Subject: Re: [PATCH v2 1/6] omap3: pm: re-program the sleep state of TRITON resources by modifying the REMAP register
Date: Thu, 21 Jan 2010 16:10:48 -0800	[thread overview]
Message-ID: <87ljfrdmnr.fsf@deeprootsystems.com> (raw)
In-Reply-To: <4B58E397.4080506@ti.com> (Mike Turquette's message of "Thu\, 21 Jan 2010 17\:30\:31 -0600")

Mike Turquette <mturquette@ti.com> writes:

> Lesly AM wrote:

[...]

>> From: "Mike Rapoport" <mike@compulab.co.il>

[...]

>>>
>>> Is it necessary to initialize the remap sleep twice?
>>>
>>
>> No.
>> Sorry..  I didn't notice that Amit has already pushed this.
>
> The existing remap programming does have a bug in it.  Lesly, try
> adding the following to this patch:

And this fix should be sent as a separate patch to Samuel and queued
as a fix for 2.6.33.

Kevin

  reply	other threads:[~2010-01-22  0:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-19 17:35 [PATCH v2 1/6] omap3: pm: re-program the sleep state of TRITON resources by modifying the REMAP register x0080970
2010-01-20 15:28 ` Mike Rapoport
2010-01-21  6:10   ` Lesly AM
2010-01-21 23:30     ` Mike Turquette
2010-01-22  0:10       ` Kevin Hilman [this message]
2010-01-22 16:41         ` Mike Turquette
2010-01-21 22:53 ` 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=87ljfrdmnr.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=dderrick@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=mike@compulab.co.il \
    --cc=mturquette@ti.com \
    --cc=nm@ti.com \
    --cc=sameo@linux.intel.com \
    --cc=x0080970@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.