From: "Pali Rohár" <pali@kernel.org>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>,
Priyanka Jain <priyanka.jain@nxp.com>,
Sinan Akman <sinan@writeme.com>, Tom Rini <trini@konsulko.com>
Cc: u-boot@lists.denx.de
Subject: Re: [PATCH 1/3] board: freescale: p1_p2_rdb_pc: Add workaround for board reset reboot loop
Date: Tue, 12 Jul 2022 15:50:54 +0200 [thread overview]
Message-ID: <20220712135054.7gemo7x5mig3ioxm@pali> (raw)
In-Reply-To: <20220705163919.rozmupridbjuzw6h@pali>
Hello! This change is waiting here since May 01.
On Tuesday 05 July 2022 18:39:19 Pali Rohár wrote:
> PING?
>
> On Sunday 01 May 2022 14:23:12 Pali Rohár wrote:
> > CPLD's system reset register on P1/P2 RDB boards is not autocleared after
> > flipping it. If this register is set to one then CPLD triggers reset of CPU
> > in few ms.
> >
> > This means that trying to reset board via CPLD system reset register cause
> > reboot loop. To prevent this reboot loop, the only workaround is to try to
> > clear CPLD's system reset register as early as possible. U-Boot is already
> > doing it in its board_early_init_f() function, which seems to be enough as
> > register is cleared prior CPLD triggers another reset.
> >
> > But board_early_init_f() is not called from SPL and therefore usage of SPL
> > can cause reboot loop.
> >
> > To prevent reboot loop when using SPL, calls board_early_init_f() function
> > in SPL too. For accessing CPLD memory space it is needed to have CPLD entry
> > in TLB.
> >
> > With this change it is possible to trigger board reset via CPLD's system
> > reset register on P2020 RDB board.
> >
> > Signed-off-by: Pali Rohár <pali@kernel.org>
> > ---
> > board/freescale/p1_p2_rdb_pc/p1_p2_rdb_pc.c | 10 ++++++++++
> > board/freescale/p1_p2_rdb_pc/spl.c | 6 ++++++
> > board/freescale/p1_p2_rdb_pc/tlb.c | 2 +-
> > 3 files changed, 17 insertions(+), 1 deletion(-)
> >
> > diff --git a/board/freescale/p1_p2_rdb_pc/p1_p2_rdb_pc.c b/board/freescale/p1_p2_rdb_pc/p1_p2_rdb_pc.c
> > index 7b168fa091b1..26ea8a525228 100644
> > --- a/board/freescale/p1_p2_rdb_pc/p1_p2_rdb_pc.c
> > +++ b/board/freescale/p1_p2_rdb_pc/p1_p2_rdb_pc.c
> > @@ -91,6 +91,16 @@ void board_cpld_init(void)
> > out_8(&cpld_data->status_led, CPLD_STATUS_LED);
> > out_8(&cpld_data->fxo_led, CPLD_FXO_LED);
> > out_8(&cpld_data->fxs_led, CPLD_FXS_LED);
> > +
> > + /*
> > + * CPLD's system reset register on P1/P2 RDB boards is not autocleared
> > + * after flipping it. If this register is set to one then CPLD triggers
> > + * reset of CPU in few ms.
> > + *
> > + * This means that trying to reset board via CPLD system reset register
> > + * cause reboot loop. To prevent this reboot loop, the only workaround
> > + * is to try to clear CPLD's system reset register as early as possible.
> > + */
> > out_8(&cpld_data->system_rst, CPLD_SYS_RST);
> > }
> >
> > diff --git a/board/freescale/p1_p2_rdb_pc/spl.c b/board/freescale/p1_p2_rdb_pc/spl.c
> > index 22156f2824ec..def28665960d 100644
> > --- a/board/freescale/p1_p2_rdb_pc/spl.c
> > +++ b/board/freescale/p1_p2_rdb_pc/spl.c
> > @@ -31,6 +31,12 @@ void board_init_f(ulong bootflag)
> > u32 plat_ratio, bus_clk;
> > ccsr_gur_t *gur = (void *)CONFIG_SYS_MPC85xx_GUTS_ADDR;
> >
> > + /*
> > + * Call board_early_init_f() as early as possible as it workarounds
> > + * reboot loop due to broken CPLD state machine for reset line.
> > + */
> > + board_early_init_f();
> > +
> > console_init_f();
> >
> > /* Set pmuxcr to allow both i2c1 and i2c2 */
> > diff --git a/board/freescale/p1_p2_rdb_pc/tlb.c b/board/freescale/p1_p2_rdb_pc/tlb.c
> > index 13f3a1edf68d..2d431d6d0d90 100644
> > --- a/board/freescale/p1_p2_rdb_pc/tlb.c
> > +++ b/board/freescale/p1_p2_rdb_pc/tlb.c
> > @@ -61,11 +61,11 @@ struct fsl_e_tlb_entry tlb_table[] = {
> > MAS3_SX|MAS3_SW|MAS3_SR, MAS2_I|MAS2_G,
> > 0, 5, BOOKE_PAGESZ_1M, 1),
> > #endif
> > +#endif /* not SPL */
> >
> > SET_TLB_ENTRY(1, CONFIG_SYS_CPLD_BASE, CONFIG_SYS_CPLD_BASE_PHYS,
> > MAS3_SX|MAS3_SW|MAS3_SR, MAS2_I|MAS2_G,
> > 0, 6, BOOKE_PAGESZ_1M, 1),
> > -#endif /* not SPL */
> >
> > #ifdef CONFIG_SYS_NAND_BASE
> > /* *I*G - NAND */
> > --
> > 2.20.1
> >
next prev parent reply other threads:[~2022-07-12 13:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-01 12:23 [PATCH 1/3] board: freescale: p1_p2_rdb_pc: Add workaround for board reset reboot loop Pali Rohár
2022-05-01 12:23 ` [PATCH 2/3] board: freescale: p1_p2_rdb_pc: Add workaround for non-working watchdog Pali Rohár
2022-05-01 12:23 ` [PATCH 3/3] board: freescale: p1_p2_rdb_pc: Implement board_reset() Pali Rohár
2022-07-05 16:39 ` [PATCH 1/3] board: freescale: p1_p2_rdb_pc: Add workaround for board reset reboot loop Pali Rohár
2022-07-12 13:50 ` Pali Rohár [this message]
2022-08-01 13:31 ` [PATCH v2 1/4] " Pali Rohár
2022-08-01 13:31 ` [PATCH v2 2/4] board: freescale: p1_p2_rdb_pc: Add workaround for non-working watchdog Pali Rohár
2022-08-01 13:31 ` [PATCH v2 3/4] board: freescale: p1_p2_rdb_pc: Avoid usage of CPLD's system reset register Pali Rohár
2022-08-01 13:31 ` [PATCH v2 4/4] board: freescale: p1_p2_rdb_pc: Turn off watchdog before reset Pali Rohár
2022-08-17 21:04 ` [PATCH v2 1/4] board: freescale: p1_p2_rdb_pc: Add workaround for board reset reboot loop Pali Rohár
2022-08-21 10:30 ` Pali Rohár
2022-08-31 12:04 ` Pali Rohár
2022-09-06 5:20 ` Peng Fan
2022-09-06 5:26 ` Peng Fan
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=20220712135054.7gemo7x5mig3ioxm@pali \
--to=pali@kernel.org \
--cc=peng.fan@oss.nxp.com \
--cc=priyanka.jain@nxp.com \
--cc=sinan@writeme.com \
--cc=trini@konsulko.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