From: Weijie Gao <weijie.gao@mediatek.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3] board_r: move initr_serial to be called before initr_watchdog
Date: Thu, 16 May 2019 17:09:19 +0800 [thread overview]
Message-ID: <1557997759.4849.70.camel@mcddlt001> (raw)
In-Reply-To: <1b46a74f-10dd-c7d7-3905-0f4e5a44d119@denx.de>
On Thu, 2019-05-16 at 10:21 +0200, Stefan Roese wrote:
> On 16.05.19 08:48, Weijie Gao wrote:
> > The initr_watchdog is currently placed before initr_serial. The
> > initr_watchdog calls printf and printf finally calls ops->putc of a serial
> > driver.
> >
> > However, gd->cur_serial_dev points to a udevice allocated in board_f. The
> > gd->cur_serial_dev->driver->ops->putc points the the code region before
> > relocation.
> >
> > Some serial drivers call WATCHDOG_RESET() in ops->putc. When DM is enabled
> > for watchdog, watchdog_reset() is called. watchdog_reset() calls get_timer
> > to get current timer.
> >
> > On some platforms the timer driver is also a DM driver. initr_watchdog is
> > placed right after initr_dm, which means the timer driver hasn't been
> > initialized. So dm_timer_init() is called. To create a new udevice, calloc
> > is called.
> >
> > However start from ops->putc, u-boot execution flow is redirected into the
> > memory region before relocation (board_f). In board_f, dlmalloc hasn't
> > been initialized. The call to calloc will fail, and this will cause DM to
> > print out an error message, and it will call printf again, causing
> > recursive error outputs.
> >
> > This patch places initr_serial before initr_watchdog to solve this issue.
> >
> > Cc: Stefan Roese <sr@denx.de>
> > Reviewed-by: Ryder Lee <ryder.lee@mediatek.com>
> > Signed-off-by: Weijie Gao <weijie.gao@mediatek.com>
> > ---
> > common/board_r.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/common/board_r.c b/common/board_r.c
> > index 150e8cd424..a298146c2b 100644
> > --- a/common/board_r.c
> > +++ b/common/board_r.c
> > @@ -678,6 +678,7 @@ static init_fnc_t init_sequence_r[] = {
> > #ifdef CONFIG_DM
> > initr_dm,
> > #endif
> > + initr_serial,
> > #if defined(CONFIG_WDT)
> > initr_watchdog,
> > #endif
> > @@ -698,7 +699,6 @@ static init_fnc_t init_sequence_r[] = {
> > efi_memory_init,
> > #endif
> > stdio_init_tables,
> > - initr_serial,
> > initr_announce,
>
> I'm not 100% sure, if moving initr_serial before stdio_init_tables and
> other functions is safe. Perhaps its better to just move initr_watchdog
> down a bit, perhaps after initr_announce?
>
> What do you think?
>
> Thanks,
> Stefan
>
> BTW: Somehow your Cc'ing me did not reach me directly. I only found the
> patch on the list.
I'll change it to move initr_watchdog only.
My company's mail server reported delivery failure every time I Cc'ed
you and some others. I have no idea.
next prev parent reply other threads:[~2019-05-16 9:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 6:48 [U-Boot] [PATCH 1/3] board_r: move initr_serial to be called before initr_watchdog Weijie Gao
2019-05-16 8:21 ` Stefan Roese
2019-05-16 9:09 ` Weijie Gao [this message]
2019-06-29 1:30 ` Suniel Mahesh
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=1557997759.4849.70.camel@mcddlt001 \
--to=weijie.gao@mediatek.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