From: "Cédric Le Goater" <clg@redhat.com>
To: qemu-arm@nongnu.org, qemu-devel@nongnu.org
Cc: "Ed Tanous" <etanous@nvidia.com>, "Cédric Le Goater" <clg@redhat.com>
Subject: [PULL 08/11] hw/arm/aspeed: Add second SPI chip to Aspeed model
Date: Fri, 4 Jul 2025 10:37:20 +0200 [thread overview]
Message-ID: <20250704083723.1410455-9-clg@redhat.com> (raw)
In-Reply-To: <20250704083723.1410455-1-clg@redhat.com>
From: Ed Tanous <etanous@nvidia.com>
Aspeed2600 has two spi lanes; Add a new struct that can mount the
second SPI.
Signed-off-by: Ed Tanous <etanous@nvidia.com>
Reviewed-by: Cédric Le Goater <clg@redhat.com>
Link: https://lore.kernel.org/qemu-devel/20250703144249.3348879-2-etanous@nvidia.com
Signed-off-by: Cédric Le Goater <clg@redhat.com>
---
include/hw/arm/aspeed.h | 2 ++
hw/arm/aspeed.c | 2 ++
2 files changed, 4 insertions(+)
diff --git a/include/hw/arm/aspeed.h b/include/hw/arm/aspeed.h
index 973277bea655..6c364556565a 100644
--- a/include/hw/arm/aspeed.h
+++ b/include/hw/arm/aspeed.h
@@ -35,7 +35,9 @@ struct AspeedMachineClass {
uint32_t hw_strap2;
const char *fmc_model;
const char *spi_model;
+ const char *spi2_model;
uint32_t num_cs;
+ uint32_t num_cs2;
uint32_t macs_mask;
void (*i2c_init)(AspeedMachineState *bmc);
uint32_t uart_default;
diff --git a/hw/arm/aspeed.c b/hw/arm/aspeed.c
index 94897505f8e3..8d7757e11f1c 100644
--- a/hw/arm/aspeed.c
+++ b/hw/arm/aspeed.c
@@ -465,6 +465,8 @@ static void aspeed_machine_init(MachineState *machine)
aspeed_board_init_flashes(&bmc->soc->spi[0],
bmc->spi_model ? bmc->spi_model : amc->spi_model,
1, amc->num_cs);
+ aspeed_board_init_flashes(&bmc->soc->spi[1],
+ amc->spi2_model, 1, amc->num_cs2);
}
if (machine->kernel_filename && sc->num_cpus > 1) {
--
2.50.0
next prev parent reply other threads:[~2025-07-04 8:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-04 8:37 [PULL 00/11] aspeed queue Cédric Le Goater
2025-07-04 8:37 ` [PULL 01/11] hw/misc/aspeed_sdmc: Skipping dram_init in u-boot for AST2700 Cédric Le Goater
2025-07-04 8:37 ` [PULL 02/11] hw/misc/aspeed_scu: Support the Frequency Counter Control register " Cédric Le Goater
2025-07-04 8:37 ` [PULL 03/11] hw/arm/aspeed: bletchley: update hw strap values Cédric Le Goater
2025-07-04 8:37 ` [PULL 04/11] hw/arm/aspeed: add Catalina machine type Cédric Le Goater
2025-07-04 8:37 ` [PULL 05/11] hw/misc/aspeed_scu: Handle AST2600 protection key registers correctly Cédric Le Goater
2025-07-04 8:37 ` [PULL 06/11] tests/qtest: Add test for ASPEED SCU Cédric Le Goater
2025-07-04 8:37 ` [PULL 07/11] aspeed: Deprecate the ast2700a0-evb machine Cédric Le Goater
2025-07-04 8:37 ` Cédric Le Goater [this message]
2025-07-04 8:37 ` [PULL 09/11] docs: add support for gb200-bmc Cédric Le Goater
2025-07-11 12:01 ` Peter Maydell
2025-07-15 6:13 ` Cédric Le Goater
2025-07-15 8:49 ` Peter Maydell
2025-07-04 8:37 ` [PULL 10/11] hw/arm/aspeed: Add GB200 BMC target Cédric Le Goater
2025-07-04 8:37 ` [PULL 11/11] tests/functional: Add gb200 tests Cédric Le Goater
2025-07-04 17:49 ` [PULL 00/11] aspeed queue Stefan Hajnoczi
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=20250704083723.1410455-9-clg@redhat.com \
--to=clg@redhat.com \
--cc=etanous@nvidia.com \
--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).