public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Mark Jackson <mpfj-list@newflow.co.uk>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2 3/4] ARM: AM33xx: Move s_init to a common place
Date: Wed, 28 Aug 2013 13:58:29 +0100	[thread overview]
Message-ID: <521DF3F5.6070301@newflow.co.uk> (raw)
In-Reply-To: <52173F93.80907@newflow.co.uk>

On 23/08/13 11:55, Mark Jackson wrote:
> On 23/08/13 11:25, Lokesh Vutla wrote:
>> Hi Mark,
>>
>> On Friday 23 August 2013 02:58 PM, Mark Jackson wrote:
>>> On 30/07/13 06:18, Lokesh Vutla wrote:
>>>> From: Heiko Schocher <hs@denx.de>
>>>>
>>>> s_init has the same outline for all the AM33xx based
>>>> board. So making it generic.
>>>> This also helps in addition of new Soc with minimal changes.
>>>>
>>>> Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
>>>> Signed-off-by: Heiko Schocher <hs@denx.de>
>>>> Signed-off-by: Tom Rini <trini@ti.com>
>>>
> 
> <snip>
> 
>>> But this fails to boot. However, if I use the old ASM code:-
>>>
>>> void enable_norboot_pin_mux(void)
>>> {
>>> 	asm("stmfd      sp!, {r2 - r4}");
>>> 	asm("movw       r4, #0x8A4");
>>> 	asm("movw       r3, #0x44E1");
>>> 	asm("orr        r4, r4, r3, lsl #16");
>>> 	asm("mov        r2, #9");
>>> 	asm("mov        r3, #8");
>>> 	asm("gpmc_mux:  str     r2, [r4], #4");
>>> 	asm("subs       r3, r3, #1");
>>> 	asm("bne        gpmc_mux");
>>> 	asm("ldmfd      sp!, {r2 - r4}");
>>> }
>> This code writes 0x9 into 8 continuous registers starting from
>> 0x44e108a4, this is what done in module_pin_mux norboot_pin_mux
>> except that it has 9 registers(i guess 9th register was added by mistake..:( )
>> Correct me if I am wrong.
> 
> Not sure about the code, but it was introduced here:-
> 
> http://git.denx.de/?p=u-boot/u-boot-ti.git;a=commit;h=c5c7a7c32d552592ac49749e5c184c89bd50c098
> 
>> So you are telling this is wrong but boots properly ?
> 
> Basically ... yes !!

Is there any update on this issue ?

I'm keen to get our board support files pushed through.

  reply	other threads:[~2013-08-28 12:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-30  5:18 [U-Boot] [PATCH V2 0/4]ARM: AM33xx: Cleanup clocks and hwinit Lokesh Vutla
2013-07-30  5:18 ` [U-Boot] [PATCH V2 1/4] ARM: AM33xx: Cleanup dplls data Lokesh Vutla
2013-07-30  7:33   ` Heiko Schocher
2013-07-30  5:18 ` [U-Boot] [PATCH V2 2/4] ARM: AM33xx: Cleanup clocks layer Lokesh Vutla
2013-07-30  7:33   ` Heiko Schocher
2013-07-30  5:18 ` [U-Boot] [PATCH V2 3/4] ARM: AM33xx: Move s_init to a common place Lokesh Vutla
2013-07-30  7:34   ` Heiko Schocher
2013-08-21 15:51     ` Mark Jackson
2013-08-21 16:26       ` Tom Rini
2013-08-23  9:28   ` Mark Jackson
2013-08-23 10:25     ` Lokesh Vutla
2013-08-23 10:55       ` Mark Jackson
2013-08-28 12:58         ` Mark Jackson [this message]
2013-07-30  5:18 ` [U-Boot] [PATCH V2 4/4] musb: Disable extra prints Lokesh Vutla
2013-07-30  7:34   ` Heiko Schocher
2013-08-16 13:34 ` [U-Boot] [PATCH V2 0/4]ARM: AM33xx: Cleanup clocks and hwinit Tom Rini

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=521DF3F5.6070301@newflow.co.uk \
    --to=mpfj-list@newflow.co.uk \
    --cc=u-boot@lists.denx.de \
    /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