All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Manuel Luís Reis" <mluis.reis@gmail.com>
To: u-boot@lists.denx.de
Subject: SAMA5D3 Xplained: SPL broken after panic added to /lib/time.c:94
Date: Fri, 2 Apr 2021 18:12:59 +0100	[thread overview]
Message-ID: <CAJYnj0ii4oPLz=VoYbCMk8FRc=OjUDVMC3ShOB8Hj6YhqdjSKw@mail.gmail.com> (raw)
In-Reply-To: <d2273891-6c98-5b4c-efac-e71b6a0205f7@microchip.com>

> As it seems from the dump of dm_dump_all() the atmel_pit_timer is not
> probed. I did a bit of debug and the dm_timer_init() ->
> uclass_first_device() -> uclass_find_first_device() found zero timers
> registered for UCLASS_TIMER. The driver is compiled.  Also checked that
> atmel_pit_timer probe function is not called at all. The question should be
> why it is not probed at all?

Hi,

So, I put objdump and puts to some good use and could backtrace the
initial error to a udelay call in ddr2_init function on mpddr.c file.
This function is called from mem_init on
sama5d3_xplained/sama5d3_xplained.c, which in turn is called from
board_init_f on spl_atmel.c.
I couldn't, however, find which timer_init function is being called
here. I still have a few to try, but disassembly gives me a pretty
empty function:

00303690 <timer_init>:
  303690:       e3a00000        mov     r0, #0
  303694:       e12fff1e        bx      lr

This work didn't give me many answers, but I got a couple of newbie questions:

Why is it calling board_init_f from spl_atmel.c and not spl_at91.c?
Isn't the latter the appropriate architecture for this board?
Do you know which timer_init function it is getting here?  Could this
be the reason timer isn't getting probed?

Cheers,

  reply	other threads:[~2021-04-02 17:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-23 11:06 SAMA5D3 Xplained: SPL broken after panic added to /lib/time.c:94 Manuel Luís Reis
2021-03-23 11:14 ` Eugen.Hristev at microchip.com
2021-03-23 11:28   ` Manuel Luís Reis
2021-03-23 11:38     ` Eugen.Hristev at microchip.com
2021-03-23 13:20       ` Manuel Luís Reis
2021-03-23 16:08         ` Manuel Luís Reis
2021-03-23 16:26           ` Eugen.Hristev at microchip.com
2021-03-23 16:54             ` Manuel Luís Reis
2021-03-24  0:34               ` Sean Anderson
2021-03-25 10:25               ` Claudiu.Beznea at microchip.com
2021-04-02 17:12                 ` Manuel Luís Reis [this message]
2021-04-02 17:15                   ` Manuel Luís Reis
2021-04-04 16:25                     ` Manuel Reis
2021-04-05 12:44                       ` Eugen.Hristev at microchip.com
2021-04-05 12:47                         ` Manuel Luís Reis
2021-04-05 13:58                           ` Eugen.Hristev at microchip.com
2021-04-05 15:42                             ` Manuel Luís Reis
2021-04-05 16:00                               ` Eugen.Hristev at microchip.com
2021-04-05 17:50                                 ` Manuel Luís Reis

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='CAJYnj0ii4oPLz=VoYbCMk8FRc=OjUDVMC3ShOB8Hj6YhqdjSKw@mail.gmail.com' \
    --to=mluis.reis@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.