From: "Cousson, Benoit" <b-cousson@ti.com>
To: Rajendra Nayak <rnayak@ti.com>
Cc: linux-omap@vger.kernel.org, Gina Glaser <g-glaser@ti.com>
Subject: Re: [PATCH] ARM: omap4: prm: Fix up swapped offset macros
Date: Mon, 7 Nov 2011 14:24:05 +0100 [thread overview]
Message-ID: <4EB7DBF5.8000305@ti.com> (raw)
In-Reply-To: <1320660386-18148-1-git-send-email-rnayak@ti.com>
Hi Rajendra,
On 11/7/2011 11:06 AM, Rajendra Nayak wrote:
> The offset macros for OMAP4_RM_RSTST and OMAP4_RM_RSTTIME
> are wrongly swapped up.
>
> Thanks to Gina Glaser for identifying and reporting this.
>
> Signed-off-by: Rajendra Nayak<rnayak@ti.com>
> Cc: Gina Glaser<g-glaser@ti.com>
> ---
> arch/arm/mach-omap2/prm44xx.h | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/prm44xx.h b/arch/arm/mach-omap2/prm44xx.h
> index 3d66ccd..aa8593e 100644
> --- a/arch/arm/mach-omap2/prm44xx.h
> +++ b/arch/arm/mach-omap2/prm44xx.h
> @@ -62,8 +62,8 @@
>
> /* OMAP4 specific register offsets */
> #define OMAP4_RM_RSTCTRL 0x0000
> -#define OMAP4_RM_RSTTIME 0x0004
> -#define OMAP4_RM_RSTST 0x0008
> +#define OMAP4_RM_RSTST 0x0004
> +#define OMAP4_RM_RSTTIME 0x0008
> #define OMAP4_PM_PWSTCTRL 0x0000
> #define OMAP4_PM_PWSTST 0x0004
In fact these defines were already defined correctly later (with a slightly different name):
/* PRM.DEVICE_PRM register offsets */
[...]
#define OMAP4_PRM_RSTST_OFFSET 0x0004
#define OMAP4430_PRM_RSTST OMAP44XX_PRM_REGADDR(OMAP4430_PRM_DEVICE_INST, 0x0004)
#define OMAP4_PRM_RSTTIME_OFFSET 0x0008
#define OMAP4430_PRM_RSTTIME OMAP44XX_PRM_REGADDR(OMAP4430_PRM_DEVICE_INST, 0x0008)
I don't know where these defines are used, but we'd better use the existing ones.
Benoit
next prev parent reply other threads:[~2011-11-07 13:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 10:06 [PATCH] ARM: omap4: prm: Fix up swapped offset macros Rajendra Nayak
2011-11-07 13:24 ` Cousson, Benoit [this message]
2011-11-08 6:22 ` Rajendra Nayak
2011-11-08 7:04 ` Rajendra Nayak
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=4EB7DBF5.8000305@ti.com \
--to=b-cousson@ti.com \
--cc=g-glaser@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=rnayak@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox