From: David Gibson <david@gibson.dropbear.id.au>
To: Greg Kurz <groug@kaod.org>
Cc: qemu-ppc@nongnu.org, "Cédric Le Goater" <clg@kaod.org>,
qemu-devel@nongnu.org
Subject: Re: [PATCH 1/2] ppc/pnv: Loop on the whole hierarchy to populate the DT with the XSCOM nodes
Date: Wed, 11 Dec 2019 10:46:09 +1100 [thread overview]
Message-ID: <20191210234609.GN207300@umbus.fritz.box> (raw)
In-Reply-To: <20191210174901.6215ddd4@bahia.tlslab.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1522 bytes --]
On Tue, Dec 10, 2019 at 05:49:01PM +0100, Greg Kurz wrote:
> On Tue, 10 Dec 2019 14:58:44 +0100
> Cédric Le Goater <clg@kaod.org> wrote:
>
> > Some PnvXScomInterface objects lie a bit deeper (PnvPBCQState) than
>
> I didn't find any trace of PnvPBCQState in the code... what is it ?
>
> > the first layer, so we need to loop on the whole object hierarchy to
> > catch them.
> >
> > Signed-off-by: Cédric Le Goater <clg@kaod.org>
> > ---
> > hw/ppc/pnv_xscom.c | 7 ++++++-
> > 1 file changed, 6 insertions(+), 1 deletion(-)
> >
> > diff --git a/hw/ppc/pnv_xscom.c b/hw/ppc/pnv_xscom.c
> > index bed41840845e..006d87e970d9 100644
> > --- a/hw/ppc/pnv_xscom.c
> > +++ b/hw/ppc/pnv_xscom.c
> > @@ -326,7 +326,12 @@ int pnv_dt_xscom(PnvChip *chip, void *fdt, int root_offset)
> > args.fdt = fdt;
> > args.xscom_offset = xscom_offset;
> >
> > - object_child_foreach(OBJECT(chip), xscom_dt_child, &args);
> > + /*
> > + * Loop on the whole object hierarchy to catch all
> > + * PnvXScomInterface objects which can lie a bit deeper the first
>
> s/deeper the first/deeper than the first/
Fixed during commit.
>
> > + * layer.
> > + */
> > + object_child_foreach_recursive(OBJECT(chip), xscom_dt_child, &args);
> > return 0;
> > }
> >
>
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-12-11 0:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 13:58 [PATCH 0/2] ppc/pnv: minor XSCOM fixes Cédric Le Goater
2019-12-10 13:58 ` [PATCH 1/2] ppc/pnv: Loop on the whole hierarchy to populate the DT with the XSCOM nodes Cédric Le Goater
2019-12-10 16:49 ` Greg Kurz
2019-12-10 17:08 ` Cédric Le Goater
2019-12-10 18:04 ` Cédric Le Goater
2019-12-10 23:46 ` David Gibson [this message]
2019-12-10 21:24 ` Greg Kurz
2019-12-10 13:58 ` [PATCH 2/2] ppc/pnv: populate the DT with realized XSCOM devices Cédric Le Goater
2019-12-10 16:53 ` Greg Kurz
2019-12-10 17:08 ` Cédric Le Goater
2019-12-10 21:24 ` Greg Kurz
2019-12-10 23:46 ` [PATCH 0/2] ppc/pnv: minor XSCOM fixes David Gibson
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=20191210234609.GN207300@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=clg@kaod.org \
--cc=groug@kaod.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).