public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH] Fix PRCM_SYSCONFIG & PRCM_REVISION addresses for 24XX
Date: Tue, 5 Jun 2007 03:28:10 -0700	[thread overview]
Message-ID: <20070605102809.GF859@atomide.com> (raw)
In-Reply-To: <20070530040243.850870657@pwsan.com>

* Paul Walmsley <paul@pwsan.com> [070529 21:04]:
> Fix OMAP24XX_PRCM_REVISION and OMAP24XX_PRCM_SYSCONFIG addresses,
> which were incorrectly using 3430 PRM_{REVISION,SYSCONFIG} addresses.
> Bug found by Richard Woodruff <r-woodruff2@ti.com>.
> 
> 
> Signed-off-by: Paul Walmsley <paul@pwsan.com>
> 
> - Paul
> 
> ---
>  arch/arm/mach-omap2/prm.h |    4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> Index: linux-omap/arch/arm/mach-omap2/prm.h
> ===================================================================
> --- linux-omap.orig/arch/arm/mach-omap2/prm.h
> +++ linux-omap/arch/arm/mach-omap2/prm.h
> @@ -31,8 +31,8 @@
>   *
>   */
>  
> -#define OMAP24XX_PRCM_REVISION		OMAP_PRM_REGADDR(OCP_MOD, 0x0004)
> -#define OMAP24XX_PRCM_SYSCONFIG		OMAP_PRM_REGADDR(OCP_MOD, 0x0014)
> +#define OMAP24XX_PRCM_REVISION		OMAP_PRM_REGADDR(OCP_MOD, 0x0000)
> +#define OMAP24XX_PRCM_SYSCONFIG		OMAP_PRM_REGADDR(OCP_MOD, 0x0010)
>  
>  #define OMAP24XX_PRCM_IRQSTATUS_MPU	OMAP_PRM_REGADDR(OCP_MOD, 0x0018)
>  #define OMAP24XX_PRCM_IRQENABLE_MPU	OMAP_PRM_REGADDR(OCP_MOD, 0x001c)

Pushing today.

Tony

      reply	other threads:[~2007-06-05 10:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070530040223.689051525@pwsan.com>
2007-05-30  4:02 ` [PATCH] Fix PRCM_SYSCONFIG & PRCM_REVISION addresses for 24XX Paul Walmsley
2007-06-05 10:28   ` Tony Lindgren [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=20070605102809.GF859@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap-open-source@linux.omap.com \
    --cc=paul@pwsan.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