From: "Cédric Le Goater" <clg@kaod.org>
To: Patrick Williams <patrick@stwcx.xyz>
Cc: Andrew Jeffery <andrew@aj.id.au>,
Peter Maydell <peter.maydell@linaro.org>,
"open list:ASPEED BMCs" <qemu-arm@nongnu.org>,
Joel Stanley <joel@jms.id.au>,
"open list:All patches CC here" <qemu-devel@nongnu.org>
Subject: Re: [PATCH 1/2] hw/arm/aspeed: allow missing spi_model
Date: Sat, 5 Mar 2022 08:53:40 +0100 [thread overview]
Message-ID: <ac68dba6-32e0-908c-c98f-7c95102b5b43@kaod.org> (raw)
In-Reply-To: <20220305000656.1944589-1-patrick@stwcx.xyz>
On 3/5/22 01:06, Patrick Williams wrote:
> Generally all BMCs will use the fmc_model to hold their own flash
> and most will have a spi_model to hold the managed system's flash,
> but not all systems do. Add a simple NULL check to allow a system
> to set the spi_model as NULL to indicate it should not be instantiated.
OK. Let's do it that way for now but we need to rework 'num_cs' in the
Aspeed SMC model and the Aspeed machines. We started with a simple
requirement (1 FMC and 1 SPI) but since, things have become more complex.
1. we should get rid of AspeedSMCState::num_cs and simply use
AspeedSMCState::max_peripherals in the SMC model. There is no need to
restrict the number devices of the controller to match the board layout.
2. aspeed_board_init_flashes() needs a better interface. May be, something
like :
static void aspeed_board_init_flashes(AspeedSMCState *s,
const char **flashtype, int count,
int unit0)
and change ->fmc_model and ->spi_model to be arrays. Ideas welcome.
Anyhow,
Reviewed-by: Cédric Le Goater <clg@kaod.org>
Thanks,
C.
> Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
> ---
> hw/arm/aspeed.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/hw/arm/aspeed.c b/hw/arm/aspeed.c
> index 11558b327b..617a1ecbdc 100644
> --- a/hw/arm/aspeed.c
> +++ b/hw/arm/aspeed.c
> @@ -276,7 +276,11 @@ static void aspeed_board_init_flashes(AspeedSMCState *s,
> const char *flashtype,
> int unit0)
> {
> - int i ;
> + int i;
> +
> + if (!flashtype) {
> + return;
> + }
>
> for (i = 0; i < s->num_cs; ++i) {
> DriveInfo *dinfo = drive_get(IF_MTD, 0, unit0 + i);
prev parent reply other threads:[~2022-03-05 7:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-05 0:06 [PATCH 1/2] hw/arm/aspeed: allow missing spi_model Patrick Williams
2022-03-05 0:06 ` [PATCH 2/2] hw/arm/aspeed: add Bletchley machine type Patrick Williams
2022-03-05 7:57 ` Cédric Le Goater
2022-03-07 20:59 ` Patrick Williams
2022-03-08 8:14 ` Cédric Le Goater
2022-03-08 17:23 ` Patrick Williams
2022-03-08 23:07 ` Joel Stanley
2022-03-05 7:53 ` Cédric Le Goater [this message]
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=ac68dba6-32e0-908c-c98f-7c95102b5b43@kaod.org \
--to=clg@kaod.org \
--cc=andrew@aj.id.au \
--cc=joel@jms.id.au \
--cc=patrick@stwcx.xyz \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).