From: Conor Dooley <conor@kernel.org>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: Bin Meng <bin.meng@windriver.com>,
Alistair Francis <alistair.francis@wdc.com>,
qemu-riscv@nongnu.org, qemu-devel@nongnu.org,
Conor Dooley <conor.dooley@microchip.com>
Subject: Re: [PATCH] hw/misc/pfsoc: add fabric clocks to ioscb
Date: Sat, 12 Nov 2022 00:30:34 +0000 [thread overview]
Message-ID: <Y27pKpA0jo67Ntlz@spud> (raw)
In-Reply-To: <84b8985a-6fab-ff76-7058-f702203474c0@linaro.org>
On Thu, Nov 10, 2022 at 12:18:44AM +0100, Philippe Mathieu-Daudé wrote:
> Hi Conor,
>
> On 9/11/22 20:08, Conor Dooley wrote:
> > From: Conor Dooley <conor.dooley@microchip.com>
> >
> > @@ -168,6 +170,10 @@ static void mchp_pfsoc_ioscb_realize(DeviceState *dev, Error **errp)
> > "mchp.pfsoc.ioscb.cfg", IOSCB_SUBMOD_REG_SIZE);
> > memory_region_add_subregion(&s->container, IOSCB_CFG_BASE, &s->cfg);
> > + memory_region_init_io(&s->ccc, OBJECT(s), &mchp_pfsoc_dummy_ops, s,
> > + "mchp.pfsoc.ioscb.ccc", IOSCB_CCC_REG_SIZE);
> > + memory_region_add_subregion(&s->container, IOSCB_CCC_BASE, &s->ccc);
>
> Unrelated but using the TYPE_UNIMPLEMENTED_DEVICE would ease tracing all
> these block accesses, as the block name would appear before the
> address/size. See for example aspeed_mmio_map_unimplemented();
Certainly looks like a nice idea, and I gave it a go but kept running
into issues due to my lack of understanding of QEMU :) I'm going to add
this to my todo pile - while I have a v2 of this lined up, I'd rather
not hold up adding the regions that prevent booting Linux etc as I
fumble around trying to understand the hierarchy of devices required to
set up something similar to your aspeed example.
Thanks,
Conor.
next prev parent reply other threads:[~2022-11-12 0:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 19:08 [PATCH] hw/misc/pfsoc: add fabric clocks to ioscb Conor Dooley
2022-11-09 23:18 ` Philippe Mathieu-Daudé
2022-11-09 23:30 ` Conor Dooley
2022-11-12 0:30 ` Conor Dooley [this message]
2022-11-12 0:37 ` Bin Meng
2022-11-12 13:19 ` Conor Dooley
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=Y27pKpA0jo67Ntlz@spud \
--to=conor@kernel.org \
--cc=alistair.francis@wdc.com \
--cc=bin.meng@windriver.com \
--cc=conor.dooley@microchip.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@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).