From: Slawomir Stepien <sst@poczta.fm>
To: Quentin Schulz <quentin.schulz@theobroma-systems.com>
Cc: Jonas Karlman <jonas@kwiboo.se>,
Kever Yang <kever.yang@rock-chips.com>,
Simon Glass <sjg@chromium.org>,
Philipp Tomsich <philipp.tomsich@vrull.eu>,
Eugen Hristev <eugen.hristev@collabora.com>,
John Clark <inindev@gmail.com>,
u-boot@lists.denx.de
Subject: Re: [PATCH 1/4] rockchip: rk3588: Fix boot from SPI flash
Date: Fri, 17 Nov 2023 15:03:39 +0100 [thread overview]
Message-ID: <ZVdyu2vjW0LrW6Jf@nr200> (raw)
In-Reply-To: <561f7d8a-bf46-4ba7-a353-b5d3dfab95b0@theobroma-systems.com>
On lis 14, 2023 15:06, Quentin Schulz wrote:
> Hi Jonas,
Hi Quentin
> On 11/12/23 11:26, Jonas Karlman wrote:
> > The commit fd6e425be243 ("rockchip: rk3588-rock-5b: Enable boot from SPI
> > NOR flash") added a new BROM_BOOTSOURCE_SPINOR_RK3588 with value 6.
> >
> > At the time the reason for this new bootsource id value 6 was unknown.
> >
> > We now know that the BootRom on RK3588 use different bootsource id
> > values depending on the iomux used by the flash spi controller, and not
> > by the type of spi nor or spi nand flash used.
> >
> > Add the following defines and use them for RK3588 boot_devices.
> >
> > - BROM_BOOTSOURCE_FSPI_M0 = 3
> > - BROM_BOOTSOURCE_FSPI_M1 = 4
> > - BROM_BOOTSOURCE_FSPI_M2 = 6
> >
> > Fixes: fd6e425be243 ("rockchip: rk3588-rock-5b: Enable boot from SPI NOR flash")
> > Signed-off-by: Jonas Karlman <jonas@kwiboo.se>
> > ---
> > arch/arm/include/asm/arch-rockchip/bootrom.h | 4 +++-
> > arch/arm/mach-rockchip/rk3588/rk3588.c | 5 +++--
> > 2 files changed, 6 insertions(+), 3 deletions(-)
> >
> > diff --git a/arch/arm/include/asm/arch-rockchip/bootrom.h b/arch/arm/include/asm/arch-rockchip/bootrom.h
> > index 7dab18fbc3fb..f78337397d63 100644
> > --- a/arch/arm/include/asm/arch-rockchip/bootrom.h
> > +++ b/arch/arm/include/asm/arch-rockchip/bootrom.h
> > @@ -47,8 +47,10 @@ enum {
> > BROM_BOOTSOURCE_EMMC = 2,
> > BROM_BOOTSOURCE_SPINOR = 3,
> > BROM_BOOTSOURCE_SPINAND = 4,
> > + BROM_BOOTSOURCE_FSPI_M0 = 3,
> > + BROM_BOOTSOURCE_FSPI_M1 = 4,
>
> I'm a bit wary of two pairs of enums sharing the same value, especially when
> we want to use them as offset in a static definition of an array.
>
> Should we #ifdef it (meh) for RK3588?
> Should we add a suffix like before for identifying RK3588-specific options?
>
> At the very least explicit that those are RK3588-specific in a comment for
> both conflicts (the ones that apply to everything except RK3588 to say to
> use only for !RK3588, and the ones that apply to RK3588 only)?
Can you say why it is so important to know that given enum is specific to given CPU here in the
header file? I think that the enums in the bootrom.h should be as generic as possible.
By using the possible enums in a static array, "solves" the problem of assigning the boot source to
specific CPU. There is not need to make such grouping in the bootrom.h.
--
Slawomir Stepien
next prev parent reply other threads:[~2023-11-17 16:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-12 10:26 [PATCH 0/4] rockchip: rk3588: Fix SPI flash bootsource id values Jonas Karlman
2023-11-12 10:26 ` [PATCH 1/4] rockchip: rk3588: Fix boot from SPI flash Jonas Karlman
2023-11-13 7:56 ` Slawomir Stepien
2023-11-14 14:06 ` Quentin Schulz
2023-11-17 14:03 ` Slawomir Stepien [this message]
2023-11-17 17:50 ` Tom Rini
2023-11-17 18:50 ` John Clark
2023-11-17 19:07 ` Tom Rini
2023-11-17 19:53 ` Jonas Karlman
2023-11-17 19:57 ` Tom Rini
2023-11-12 10:26 ` [PATCH 2/4] rockchip: rk3588-nanopc-t6: Build SPI image Jonas Karlman
2023-11-12 10:26 ` [PATCH 3/4] rockchip: rk3588-orangepi-5-plus: " Jonas Karlman
2023-11-12 10:27 ` [PATCH 4/4] rockchip: rk3588s-orangepi-5: " Jonas Karlman
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=ZVdyu2vjW0LrW6Jf@nr200 \
--to=sst@poczta.fm \
--cc=eugen.hristev@collabora.com \
--cc=inindev@gmail.com \
--cc=jonas@kwiboo.se \
--cc=kever.yang@rock-chips.com \
--cc=philipp.tomsich@vrull.eu \
--cc=quentin.schulz@theobroma-systems.com \
--cc=sjg@chromium.org \
--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