public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Lokesh Vutla <lokeshvutla@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm, am33xx: move s_init to a common place
Date: Mon, 24 Jun 2013 09:31:42 +0530	[thread overview]
Message-ID: <51C7C4A6.30200@ti.com> (raw)
In-Reply-To: <51C27C86.3010000@denx.de>

Hi Heiko,
On Thursday 20 June 2013 09:22 AM, Heiko Schocher wrote:
> Hello Tom,
>
> Am 14.06.2013 16:58, schrieb Tom Rini:
>> On Fri, Jun 14, 2013 at 07:59:26AM +0200, Heiko Schocher wrote:
>>> Hello Tom,
>>>
>>> Am 13.06.2013 17:53, schrieb Tom Rini:
>>>> On Thu, Jun 13, 2013 at 05:53:17AM +0200, Heiko Schocher wrote:
>>>>
>>>>> move s_init from every board code to a common place.
>>>>>
>>>>> Signed-off-by: Heiko Schocher <hs@denx.de>
>>>>> Cc: Tom Rini <trini@ti.com>
>>>>> Cc: Matt Porter <mporter@ti.com>
>>>>> Cc: Lars Poeschel <poeschel@lemonage.de>
>>>>> Cc: Tom Rini <trini@ti.com>
>>>>> Cc: Enric Balletbo i Serra <eballetbo@iseebcn.com>
>>>>>
>>>>> ---
>>>>> This patch is based on the following patches:
>>>>>
>>>>> - [U-Boot,v2] arm, am33xx: move rtc32k_enable() to common place
>>>>>    http://patchwork.ozlabs.org/patch/248908/
>>>>>
>>>>> - [U-Boot] arm, am33xx: move uart soft reset code to common place
>>>>>    http://patchwork.ozlabs.org/patch/248508/
>>>>
>>>> These two apply best to u-boot-ti, and with them this patch doesn't
>>>> apply cleanly.  Please sort that out.
>>>
>>> I based my patches on u-boot ... I look at this ..
>>>
>>>> The following adds moving ti814x_evm into the mix and I've sent Matt
>>>> some binaries to give a whirl to test on the board:
>>>>
>>> [...]
>>>>   /*
>>>>    * Basic board specific setup.  Pinmux has been handled already.
>>>>
>>>> Please fold into v2
>>>>
>>>> Signed-off-by: Tom Rini <trini@ti.com>
>>>
>>> Ok, thanks!
>>
>> There's a minor bug in what I posted, however.  ti814x needs timer_init
>> called _before_ pll_init() as setting the sata clocks (which are shared
>> with other periphrals that we do enable right now) needs udelay(50) to
>> settle as we go along.  That also needs to be commented in the code as I
>> had to think about it for a bit to recall exactly what was going on.
>
> Do you have an update here for me?
We can have a timer_init for am33xx boards also. It doesn't harm.
So keep timer_init in your common s_init
>
>>> BTW:
>>> I just realized that I have on one of the three boards a problem,
>>> that in spl code calling the rtc32k_enable() crashes ... which
>>> votes against moving this to a common place ... I haveno real idea
>>> why ... did you heard from such a behaviour? Is there some am335x
>>> soc, which differs from the others?
On which board it is giving a problem?
Did you make sure clocks for rtc are enabled?
I am making a cleanup series for am33xx boards. If you don't mind can I 
take this
patch as part of my series.

Thanks and regards,
Lokesh
>>
>> You aren't using a different clock crystal rate than the reference
>> platforms, are you?  I know that's a problem that needs solving still.
>
> I am prospecting, whats going on here ... but have no real idea,
> why it is not possible to write this registers ... if writing this
> registers, cpu hang ...
>
> But I want to have a common function here ... maybe it is OK to make
> the rtc32k_enable() call configurable through a define?
>
> Saying "CONFIG_SPL_AM33XX_DO_NOT_ENABLE_RTC32K"
>
> and document in the u-boot README this define, and why it is
> necessary?
>
> bye,
> Heiko
>

  reply	other threads:[~2013-06-24  4:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-13  3:53 [U-Boot] [PATCH] arm, am33xx: move s_init to a common place Heiko Schocher
2013-06-13 15:53 ` Tom Rini
2013-06-14  5:59   ` Heiko Schocher
2013-06-14 14:58     ` Tom Rini
2013-06-15 20:54       ` Peter Korsgaard
2013-06-20  3:52       ` Heiko Schocher
2013-06-24  4:01         ` Lokesh Vutla [this message]
2013-06-24 16:16           ` Heiko Schocher
2013-06-24 17:25             ` Lokesh Vutla

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=51C7C4A6.30200@ti.com \
    --to=lokeshvutla@ti.com \
    --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