public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: Peter 'p2' De Schrijver <peter.de-schrijver@nokia.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH] OMAP3 PM restore observability settings after off mode
Date: Tue, 13 Oct 2009 14:08:39 -0700	[thread overview]
Message-ID: <877huzhui0.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1255359790-10407-1-git-send-email-peter.de-schrijver@nokia.com> (Peter De Schrijver's message of "Mon\, 12 Oct 2009 18\:03\:10 +0300")

"Peter 'p2' De Schrijver" <peter.de-schrijver@nokia.com> writes:

> This patch restores the observability settings after resuming from off mode.
>
> Signed-off-by: Peter 'p2' De Schrijver <peter.de-schrijver@nokia.com>

I decided not to pull this one into PM branch, because...

> diff --git a/arch/arm/mach-omap2/pm34xx.c b/arch/arm/mach-omap2/pm34xx.c
> index 553fe02..20c7ea2 100644
> --- a/arch/arm/mach-omap2/pm34xx.c
> +++ b/arch/arm/mach-omap2/pm34xx.c
> @@ -42,6 +42,7 @@
>  #include <mach/dma.h>
>  #include <mach/gpmc.h>
>  #include <mach/dma.h>
> +#include <mach/debobs.h>
>  #include <asm/tlbflush.h>
>  
>  #include "cm.h"
> @@ -124,6 +125,9 @@ static void omap3_core_restore_context(void)
>  	/* Restore the interrupt controller context */
>  	omap3_intc_restore_context();
>  	omap_dma_global_context_restore();
> +	/* restore debobs context */
> +	debobs_restore();
> +

of compile failure when CONFIG_PM_DEBOBS is not enabled.

And, debobs should now go upstream indepenent of PM branch.

When I posted my PM debug series for the last merge window, I
originally included the debobs series.  It recieved some comments on
the list that need to be addressed before this can go upstream.

Now that the main PM debug stuff is in mainline, this series has no
more dependencies on the PM branch.  I think you should address the
the comments/questions raised on the list[1,2] and resubmit as a
series against mainline.

A quick test shows that the current set of 3 debobs patches currently
in the PM branch rebase easily against omap/master so should be easy
to rework for upstream acceptance.

Thanks,

Kevin

[1] http://marc.info/?l=linux-omap&m=125049645823777&w=2
[2] http://marc.info/?l=linux-omap&m=125049651623911&w=2

      parent reply	other threads:[~2009-10-13 21:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-12 15:03 [PATCH] OMAP3 PM restore observability settings after off mode Peter 'p2' De Schrijver
2009-10-13 19:23 ` Kevin Hilman
2009-10-13 21:08 ` Kevin Hilman [this message]

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=877huzhui0.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=peter.de-schrijver@nokia.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