linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jean.pihet@newoldbits.com (Jean Pihet)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/7] OMAP2+: use global values for the SRAM PA addresses
Date: Fri, 17 Dec 2010 15:59:00 +0100	[thread overview]
Message-ID: <AANLkTimYoa3baXbcwOOx-xXLXiEbKmiEWj1xR3xVCC=+@mail.gmail.com> (raw)
In-Reply-To: <4D0B66ED.8030302@ti.com>

Hi Nishant,

On Fri, Dec 17, 2010 at 2:34 PM, Nishanth Menon <nm@ti.com> wrote:
> jean.pihet at newoldbits.com had written, on 12/17/2010 04:08 AM, the
> following:
>>
>> From: Jean Pihet <j-pihet@ti.com>
>>
>> The SRAM PA addresses are locally defined and used at
>> different places, i.e. SRAM management code and idle sleep code.
>>
>> The macros are now defined at a centralized place, for
>> easier maintenance.
>>
>> Tested on N900 and Beagleboard with full RET and OFF modes,
>> using cpuidle and suspend.
>>
>> Signed-off-by: Jean Pihet <j-pihet@ti.com>
>> ---
>> ?arch/arm/mach-omap2/sdrc.h ? ? ? ? ? ? | ? ?1 -
>> ?arch/arm/mach-omap2/sleep34xx.S ? ? ? ?| ? ?1 +
>> ?arch/arm/plat-omap/include/plat/sram.h | ? 11 +++++++++++
>> ?arch/arm/plat-omap/sram.c ? ? ? ? ? ? ?| ? ?7 ++-----
>> ?4 files changed, 14 insertions(+), 6 deletions(-)
>>
>> diff --git a/arch/arm/mach-omap2/sdrc.h b/arch/arm/mach-omap2/sdrc.h
>> index 68f57bb..b3f8379 100644
>> --- a/arch/arm/mach-omap2/sdrc.h
>> +++ b/arch/arm/mach-omap2/sdrc.h
>> @@ -74,5 +74,4 @@ static inline u32 sms_read_reg(u16 reg)
>> ?*/
>> ?#define SDRC_MPURATE_LOOPS ? ? ? ? ? ? 96
>> ?-
>
> spurious change.
Cosmetic change!

>
> [...]
>
>> diff --git a/arch/arm/plat-omap/sram.c b/arch/arm/plat-omap/sram.c
>> index 819ea0c..1a686c8 100644
>> --- a/arch/arm/plat-omap/sram.c
>> +++ b/arch/arm/plat-omap/sram.c
>> @@ -41,15 +41,12 @@
>> ?#define OMAP1_SRAM_PA ? ? ? ? 0x20000000
>> ?#define OMAP1_SRAM_VA ? ? ? ? ?VMALLOC_END
>> -#define OMAP2_SRAM_PA ? ? ? ? ?0x40200000
>> -#define OMAP2_SRAM_PUB_PA ? ? ?0x4020f800
>> +#define OMAP2_SRAM_PUB_PA ? ? ?(OMAP2_SRAM_PA + 0xf800)
>> ?#define OMAP2_SRAM_VA ? ? ? ? ?0xfe400000
>> ?#define OMAP2_SRAM_PUB_VA ? ? ?(OMAP2_SRAM_VA + 0x800)
>> -#define OMAP3_SRAM_PA ? ? ? ? ? 0x40200000
>> ?#define OMAP3_SRAM_VA ? ? ? ? ? 0xfe400000
>> -#define OMAP3_SRAM_PUB_PA ? ? ? 0x40208000
>> +#define OMAP3_SRAM_PUB_PA ? ? ? (OMAP3_SRAM_PA + 0x8000)
>
> Though not directly related to the patch, information sake: the PUB physical
> address on a GP device != public SRAM address on a HS/EMU device - in theory
> PPA can reconfigure how much is available for a HS/EMU device here.
Ok good to know.

>
>> ?#define OMAP3_SRAM_PUB_VA ? ? ? (OMAP3_SRAM_VA + 0x8000)
>> -#define OMAP4_SRAM_PA ? ? ? ? ?0x40300000
>> ?#define OMAP4_SRAM_VA ? ? ? ? ?0xfe400000
>> ?#define OMAP4_SRAM_PUB_PA ? ? ?(OMAP4_SRAM_PA + 0x4000)
>> ?#define OMAP4_SRAM_PUB_VA ? ? ?(OMAP4_SRAM_VA + 0x4000)
>
> Tested-by: Nishanth Menon<nm@ti.com>
> Tested on:
> SDP3630
> SDP3430
> Test script:
> http://pastebin.mozilla.org/889933
Nice test script btw

>
> --
> Regards,
> Nishanth Menon
>

Thanks!
Jean

  reply	other threads:[~2010-12-17 14:59 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-17 10:08 [PATCH 0/7 v5] OMAP3: clean up ASM sleep code jean.pihet at newoldbits.com
2010-12-17 10:08 ` [PATCH 1/7] OMAP3: remove unused code from the " jean.pihet at newoldbits.com
2010-12-17 10:36   ` Santosh Shilimkar
2010-12-17 13:18   ` Nishanth Menon
2010-12-17 10:08 ` [PATCH 2/7] OMAP2+: use global values for the SRAM PA addresses jean.pihet at newoldbits.com
2010-12-17 10:36   ` Santosh Shilimkar
2010-12-17 13:34   ` Nishanth Menon
2010-12-17 14:59     ` Jean Pihet [this message]
2010-12-17 15:00       ` Nishanth Menon
2010-12-17 10:08 ` [PATCH 3/7] OMAP3: remove hardcoded values from the ASM sleep code jean.pihet at newoldbits.com
2010-12-17 10:36   ` Santosh Shilimkar
2010-12-17 13:51   ` Nishanth Menon
2010-12-17 10:08 ` [PATCH 4/7] OMAP3: re-organize " jean.pihet at newoldbits.com
2010-12-17 10:37   ` Santosh Shilimkar
2010-12-17 14:05   ` Nishanth Menon
2010-12-17 10:08 ` [PATCH 5/7] OMAP3: rework of the ASM sleep code execution paths jean.pihet at newoldbits.com
2010-12-17 10:37   ` Santosh Shilimkar
2010-12-17 15:35   ` Nishanth Menon
2010-12-18 15:54     ` Jean Pihet
2010-12-17 10:08 ` [PATCH 6/7] OMAP3: add comments for low power code errata jean.pihet at newoldbits.com
2010-12-17 10:37   ` Santosh Shilimkar
2010-12-17 15:43   ` Nishanth Menon
2010-12-17 10:08 ` [PATCH 7/7] OMAP3: ASM sleep code format rework jean.pihet at newoldbits.com
2010-12-17 10:37   ` Santosh Shilimkar
2010-12-17 15:58   ` Nishanth Menon
2010-12-18 15:56     ` Jean Pihet
2010-12-17 23:02 ` [PATCH 0/7 v5] OMAP3: clean up ASM sleep code Kevin Hilman
2010-12-17 23:07   ` Jean Pihet
2010-12-17 23:22     ` Nishanth Menon
2010-12-18 15:51       ` Jean Pihet
  -- strict thread matches above, loose matches on Subject: below --
2010-12-18 15:44 [PATCH 0/7 v6] " jean.pihet at newoldbits.com
2010-12-18 15:44 ` [PATCH 2/7] OMAP2+: use global values for the SRAM PA addresses jean.pihet at newoldbits.com
2010-12-16 17:50 [PATCH 0/7 v4] OMAP3: clean up ASM sleep code jean.pihet at newoldbits.com
2010-12-16 17:50 ` [PATCH 2/7] OMAP2+: use global values for the SRAM PA addresses jean.pihet at newoldbits.com
2010-12-17  4:48   ` Santosh Shilimkar
2010-12-17 10:13     ` Jean Pihet

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='AANLkTimYoa3baXbcwOOx-xXLXiEbKmiEWj1xR3xVCC=+@mail.gmail.com' \
    --to=jean.pihet@newoldbits.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).