From: Quentin Schulz <quentin.schulz@cherry.de>
To: Jonas Karlman <jonas@kwiboo.se>,
Kever Yang <kever.yang@rock-chips.com>,
Tom Rini <trini@konsulko.com>, Simon Glass <sjg@chromium.org>,
Philipp Tomsich <philipp.tomsich@vrull.eu>
Cc: u-boot@lists.denx.de
Subject: Re: [PATCH] rockchip: rk3308: Drop unused rk_board_init()
Date: Wed, 6 Nov 2024 14:49:01 +0100 [thread overview]
Message-ID: <ef7ac63b-0792-402b-8dfd-d15ccf427cd7@cherry.de> (raw)
In-Reply-To: <20241102204516.3633375-1-jonas@kwiboo.se>
Hi Jonas,
On 11/2/24 9:45 PM, Jonas Karlman wrote:
> Nothing is calling the function rk_board_init() and the io-domain driver
> can handle the functions intended purpose based on information from DT.
>
> Cleanup by removing the unused rk_board_init() function and re-sort
> included headers.
>
> Signed-off-by: Jonas Karlman <jonas@kwiboo.se>
git log -p -S rk_board_init
only returns one match and it's the introducing commit in which this
function seemingly is never called.
I'm really wondering why this wasn't shown as a warning by GCC?
Since this is the IO domain for storage medium on RK3308, shouldn't we
make sure the IO domain is enabled in SPL for fallback mechanism (i.e.
proper isn't found on the same storage medium as the one used for
loading SPL)?
The IODOMAIN isn't even enabled in proper for the EVB and the ROC-CC
board. And there isn't an IODOMAIN symbol for SPL in Kconfig AFAICT?
Not that this commit would change anything, so:
Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>
Thanks!
Quentin
next prev parent reply other threads:[~2024-11-06 13:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-02 20:45 [PATCH] rockchip: rk3308: Drop unused rk_board_init() Jonas Karlman
2024-11-06 13:49 ` Quentin Schulz [this message]
2024-11-06 21:14 ` Jonas Karlman
2024-11-07 1:45 ` Kever Yang
2024-11-11 9:41 ` Jonas Karlman
2024-11-11 10:09 ` Kever Yang
2025-02-28 11:17 ` Kever Yang
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=ef7ac63b-0792-402b-8dfd-d15ccf427cd7@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=jonas@kwiboo.se \
--cc=kever.yang@rock-chips.com \
--cc=philipp.tomsich@vrull.eu \
--cc=sjg@chromium.org \
--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