From: "Cédric Le Goater" <clg@kaod.org>
To: "Cédric Le Goater" <clg@redhat.com>,
qemu-arm@nongnu.org, qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
Joel Stanley <joel@jms.id.au>,
Andrew Jeffery <andrew@codeconstruct.com.au>,
Jamin Lin <jamin_lin@aspeedtech.com>
Subject: Re: [PATCH] aspeed/sdmc: Check RAM size value at realize time
Date: Tue, 2 Jul 2024 07:57:08 +0200 [thread overview]
Message-ID: <9399eeb7-bf05-4b8f-8d6f-b8d4511320bc@kaod.org> (raw)
In-Reply-To: <20240625065839.485034-1-clg@redhat.com>
On 6/25/24 8:58 AM, Cédric Le Goater wrote:
> The RAM size of the SDMC device is validated for the SoC and set when
> the Aspeed machines are initialized and then later used by several
> SoC implementations. However, the SDMC model never checks that the RAM
> size has been actually set before being used. Do that at realize.
>
> Signed-off-by: Cédric Le Goater <clg@redhat.com>
Applied to aspeed-next.
Thanks,
C.
> ---
> hw/misc/aspeed_sdmc.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/hw/misc/aspeed_sdmc.c b/hw/misc/aspeed_sdmc.c
> index 94eed9264d09..ebf139cb5c91 100644
> --- a/hw/misc/aspeed_sdmc.c
> +++ b/hw/misc/aspeed_sdmc.c
> @@ -271,6 +271,12 @@ static void aspeed_sdmc_realize(DeviceState *dev, Error **errp)
> AspeedSDMCClass *asc = ASPEED_SDMC_GET_CLASS(s);
>
> assert(asc->max_ram_size < 4 * GiB || asc->is_bus64bit);
> +
> + if (!s->ram_size) {
> + error_setg(errp, "RAM size is not set");
> + return;
> + }
> +
> s->max_ram_size = asc->max_ram_size;
>
> memory_region_init_io(&s->iomem, OBJECT(s), &aspeed_sdmc_ops, s,
prev parent reply other threads:[~2024-07-02 5:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 6:58 [PATCH] aspeed/sdmc: Check RAM size value at realize time Cédric Le Goater
2024-06-25 7:24 ` Jamin Lin
2024-07-02 5:57 ` 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=9399eeb7-bf05-4b8f-8d6f-b8d4511320bc@kaod.org \
--to=clg@kaod.org \
--cc=andrew@codeconstruct.com.au \
--cc=clg@redhat.com \
--cc=jamin_lin@aspeedtech.com \
--cc=joel@jms.id.au \
--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).