| commit | c29dd0034deafc9772eb256f7b4cea16c5bffd65 | |
| author | Cédric Le Goater <clg@kaod.org> | |
| Wed, 12 Jan 2022 10:28:27 +0000 (12 11:28 +0100) | ||
| committer | Cédric Le Goater <clg@kaod.org> | |
| Wed, 12 Jan 2022 10:28:27 +0000 (12 11:28 +0100) | ||
| tree | 7d4b6e368629d2c3c352b1d03c3042546b9b6e1e | treesnapshot (tar.gz zip) |
| parent | 1f6a88fffc7533a9fd64c74c298d82590277cb3b | commitdiff |
ppc/pnv: Reparent user created PHB3 devices to the PnvChip
The powernv machine uses the object hierarchy to populate the device
tree and each device should be parented to the chip it belongs to.
This is not the case for user created devices which are parented to
the container "/unattached".
Make sure a PHB3 device is parented to its chip by reparenting the
object if necessary.
Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
Reviewed-by: Frederic Barrat <fbarrat@linux.ibm.com>
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20220105212338.49899-8-danielhb413@gmail.com>
Signed-off-by: Cédric Le Goater <clg@kaod.org>
The powernv machine uses the object hierarchy to populate the device
tree and each device should be parented to the chip it belongs to.
This is not the case for user created devices which are parented to
the container "/unattached".
Make sure a PHB3 device is parented to its chip by reparenting the
object if necessary.
Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
Reviewed-by: Frederic Barrat <fbarrat@linux.ibm.com>
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20220105212338.49899-8-danielhb413@gmail.com>
Signed-off-by: Cédric Le Goater <clg@kaod.org>
| hw/pci-host/pnv_phb3.c | diffblobblamehistory | |
| hw/ppc/pnv.c | diffblobblamehistory | |
| include/hw/ppc/pnv.h | diffblobblamehistory |