From: "Cédric Le Goater" <email@example.com>
Cc: Peter Maydell <firstname.lastname@example.org>,
email@example.com, firstname.lastname@example.org, email@example.com,
Joel Stanley <firstname.lastname@example.org>
Subject: Re: [PATCH 0/1] hw/arm/aspeed: Allow machine to set serial_hd(0)
Date: Wed, 1 Sep 2021 08:44:41 +0200 [thread overview]
Message-ID: <email@example.com> (raw)
On 9/1/21 1:31 AM, firstname.lastname@example.org wrote:
> From: Peter Delevoryas <email@example.com>
> This is a follow-up to a discussion in a previous series I sent:
> I tried to add a new machine type called Fuji that required the ability
> to specify the UART connected to the first serial device on the command
> line (serial_hd(0)).
> After some discussion, we concluded that we could add a serial_dev
> option to the machine class and the SoC to support this:
> I didn't follow Cedric's advice _exactly_, so let me know if you have
> suggestions. I used "uint32_t serial_hd0", because I think it more
> clearly indicates that this is the device to connect to the first serial
> device, serial_hd(0).
I don't have a strong opinion on the name but it is part of the user
API and can be set from the command line :
I would prefer something like "uart-default" which makes more sense.
> Also, I didn't know how to transfer data from the machine class to the
> device state, so I just added the attribute to the machine class and
> used 'qdev_get_machine' to within aspeed_soc_realize() based on some
> code I found in hw/ppc/spapr_cpu_core.c.
This is called from the reset execution path which is a bit special.
The use of qdev_get_machine() should be avoided when possible.
> I expect that I'm missing
> something, I've just been having some trouble figuring out the QEMU
> object model.
Look at the "dram" property of the SoC.
> If this patch is accepted, I can follow-up with another patch adding the
> fuji machine type with "serial_hd0 = ASPEED_DEV_UART1".
> Peter Delevoryas (1):
> hw/arm/aspeed: Allow machine to set serial_hd(0)
> hw/arm/aspeed.c | 1 +
> hw/arm/aspeed_ast2600.c | 11 +++++++----
> hw/arm/aspeed_soc.c | 9 ++++++---
> include/hw/arm/aspeed.h | 1 +
> 4 files changed, 15 insertions(+), 7 deletions(-)
prev parent reply other threads:[~2021-09-01 6:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 23:31 [PATCH 0/1] hw/arm/aspeed: Allow machine to set serial_hd(0) pdel
2021-08-31 23:31 ` [PATCH 1/1] " pdel
2021-09-01 2:30 ` Patrick Williams
2021-09-01 6:34 ` Cédric Le Goater
2021-09-01 14:05 ` Peter Delevoryas
2021-09-01 6:44 ` Cédric Le Goater [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.