From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH 2/4] board: ns3: Remove superfluous reset logic
Date: Wed, 3 Mar 2021 14:08:26 -0500 [thread overview]
Message-ID: <20210303190826.GK1310@bill-the-cat> (raw)
In-Reply-To: <b38936fe0042e2ad158e922cc6a8a1a70332b9c4.1608045173.git.hws@denx.de>
On Tue, Dec 15, 2020 at 04:47:50PM +0100, Harald Seiler wrote:
> The current implementation of reset_cpu() in the ns3 board code does not
> archieve what it is supposed to (according to the comments), due to
> a number of reasons:
>
> 1. The argument to reset_cpu() is _not_ actually passed from the
> `reset` command, but is set to 0 in all call-sites (in this
> specific case, see arch/arm/lib/reset.c). Thus, performing
> different kinds of resets based on its value will not work as
> expected.
>
> 2. Contrary to its documentation, the passed argument is not
> interpreted, but a static `L3_RESET` define is used. The other
> comment properly notes that this will always perform a L3 reset,
> though.
>
> 3. The "parsing" of the static `L3_RESET` value is not even using the
> upper and lower nibble as stated in the comment, but uses the last
> two decimal digits of the value.
>
> This is currently one of the only implementations left in U-Boot, which
> make "use" of the value passed to reset_cpu(). As this is done under
> false assumption (the value does not have any meaning anymore), it makes
> sense to bring it into line with the rest and start ignoring the
> parameter.
>
> This is a preparation for removal of the reset_cpu() parameter across
> the entire tree in a later patch.
>
> Fixes: b5a152e7ca0b ("board: ns3: default reset type to L3")
> Cc: Bharat Gooty <bharat.gooty@broadcom.com>
> Cc: Rayagonda Kokatanur <rayagonda.kokatanur@broadcom.com>
> Signed-off-by: Harald Seiler <hws@denx.de>
> Reviewed-by: Simon Glass <sjg@chromium.org>
(Er, 1/4 had the wrong branch ...)
Applied to u-boot/next, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20210303/88c612a3/attachment.sig>
next prev parent reply other threads:[~2021-03-03 19:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 15:47 [PATCH 0/4] Remove addr parameter from reset_cpu() Harald Seiler
2020-12-15 15:47 ` [PATCH 1/4] nds32: Remove dead reset_cpu() implementation Harald Seiler
2020-12-19 2:28 ` Simon Glass
[not found] ` <752D002CFF5D0F4FA35C0100F1D73F3FB28D18D9@ATCPCS16.andestech.com>
2020-12-21 0:33 ` Rick Chen
2021-03-03 19:07 ` Tom Rini
2020-12-15 15:47 ` [PATCH 2/4] board: ns3: Remove superfluous reset logic Harald Seiler
2020-12-19 2:28 ` Simon Glass
2021-03-03 19:08 ` Tom Rini [this message]
2020-12-15 15:47 ` [PATCH 3/4] Revert "lpc32xx: cpu: add support for soft reset" Harald Seiler
2020-12-15 17:29 ` Sylvain Lemieux
2020-12-17 10:09 ` Harald Seiler
2020-12-17 14:33 ` Sylvain Lemieux
2021-03-03 19:08 ` Tom Rini
2020-12-15 15:47 ` [PATCH 4/4] reset: Remove addr parameter from reset_cpu() Harald Seiler
2020-12-19 2:28 ` Simon Glass
2021-03-03 19:08 ` Tom Rini
2021-03-02 11:35 ` [PATCH 0/4] " Harald Seiler
2021-03-05 4:08 ` Simon Glass
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=20210303190826.GK1310@bill-the-cat \
--to=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