public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Rajendra Nayak <rnayak@ti.com>
To: "Cousson, Benoit" <b-cousson@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: Tue, 08 Nov 2011 12:34:58 +0530	[thread overview]
Message-ID: <4EB8D49A.8040605@ti.com> (raw)
In-Reply-To: <4EB8CA93.3020706@ti.com>

On Tuesday 08 November 2011 11:52 AM, Rajendra Nayak wrote:
>>>
>>> /* 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.
>
> Yes, it looks like it makes sense to completely get rid of these and
> instead use the auto-generated ones.
> I see there are these multiple defines for omap3 too, maybe its best to
> get rid of them for omap3 too?

Looking at it a little more closely, I now see why some of these
are needed.

#define OMAP4_PM_PWSTCTRL                               0x0000
#define OMAP4_PM_PWSTST                                 0x0004

These seem to be needed because the autogen output throws out offsets
with the individual domain names embedded, which can't be used in
generic powerdomain code, and since all of them are the same, the
ones with the individual domain names never get used.
Maybe a case for the autogen script updates to get rid of all those and
just generate something like the above. Should give some good -ve
diffstat :)

#define OMAP4_RM_RSTCTRL                                0x0000
#define OMAP4_RM_RSTTIME                                0x0004

These don't seem to be used at all.

#define OMAP4_RM_RSTST                                  0x0008

The only instance of this being used I see is in 
omap_prcm_get_reset_sources() and seems completely wrong
as its using a omap2/3 api (omap2_prm_read_mod_reg())
on omap4.

>
>>
>> Benoit
>


      reply	other threads:[~2011-11-08  7:05 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
2011-11-08  6:22   ` Rajendra Nayak
2011-11-08  7:04     ` Rajendra Nayak [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=4EB8D49A.8040605@ti.com \
    --to=rnayak@ti.com \
    --cc=b-cousson@ti.com \
    --cc=g-glaser@ti.com \
    --cc=linux-omap@vger.kernel.org \
    /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