Bernhard Beschow <[email protected]> writes: > Rather than having a NULL parent, let the containing SoC object be the > parent. This cleans up the QOM composition tree a bit. > > Fixes: 1aaf3478684f ("hw/arm/fsl-imx8mp: Add on-chip RAM") > cc: Gaurav Sharma <[email protected]> > Signed-off-by: Bernhard Beschow <[email protected]> > --- > hw/arm/fsl-imx8mp.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/hw/arm/fsl-imx8mp.c b/hw/arm/fsl-imx8mp.c > index 0119a18416..839c925e4a 100644 > --- a/hw/arm/fsl-imx8mp.c > +++ b/hw/arm/fsl-imx8mp.c > @@ -671,7 +671,7 @@ static void fsl_imx8mp_realize(DeviceState *dev, Error > **errp) > fsl_imx8mp_memmap[FSL_IMX8MP_PCIE_PHY1].addr); > > /* On-Chip RAM */ > - if (!memory_region_init_ram(&s->ocram, NULL, "imx8mp.ocram", > + if (!memory_region_init_ram(&s->ocram, OBJECT(dev), "imx8mp.ocram", > fsl_imx8mp_memmap[FSL_IMX8MP_OCRAM].size, > errp)) { > return;
This moves /machine/unattached/imx8mp.ocram[0] to /machine/soc/imx8mp.ocram[0], as expected. Reviewed-by: Markus Armbruster <[email protected]> Aside: not sure why [0]. Might just be something memory regions do.
