Hi Cédric, > -----Original Message----- > From: Steven Lee > Sent: Thursday, May 15, 2025 1:06 PM > To: Cédric Le Goater <c...@redhat.com>; Peter Maydell > <peter.mayd...@linaro.org>; Troy Lee <leet...@gmail.com>; Jamin Lin > <jamin_...@aspeedtech.com>; Andrew Jeffery > <and...@codeconstruct.com.au>; Joel Stanley <j...@jms.id.au>; open > list:ASPEED BMCs <qemu-...@nongnu.org>; open list:All patches CC here > <qemu-devel@nongnu.org> > Cc: Troy Lee <troy_...@aspeedtech.com>; long...@lenovo.com; Yunlin Tang > <yunlin.t...@aspeedtech.com> > Subject: RE: [PATCH v2 2/5] hw/arm/aspeed_ast27x0: Fix unimplemented > region overlap with vbootrom > > Hi Cédric, > > > -----Original Message----- > > From: Cédric Le Goater <c...@redhat.com> > > Sent: Wednesday, May 14, 2025 9:28 PM > > To: Steven Lee <steven_...@aspeedtech.com>; Peter Maydell > > <peter.mayd...@linaro.org>; Troy Lee <leet...@gmail.com>; Jamin Lin > > <jamin_...@aspeedtech.com>; Andrew Jeffery > > <and...@codeconstruct.com.au>; Joel Stanley <j...@jms.id.au>; open > > list:ASPEED BMCs <qemu-...@nongnu.org>; open list:All patches CC here > > <qemu-devel@nongnu.org> > > Cc: Troy Lee <troy_...@aspeedtech.com>; long...@lenovo.com; Yunlin > > Tang <yunlin.t...@aspeedtech.com> > > Subject: Re: [PATCH v2 2/5] hw/arm/aspeed_ast27x0: Fix unimplemented > > region overlap with vbootrom > > > > On 5/14/25 11:03, Steven Lee wrote: > > > The unimplemented memory region overlaps with the VBootROM address > > > range, causing incorrect memory layout and potential behavior issues. > > > > > > This patch adjusts the size and start address of the unimplemented > > > region to avoid collision. The IO memory region (ASPEED_DEV_IOMEM) > > > is now moved to 0x20000 to reserve space for VBootROM at 0x0. > > > > > > Signed-off-by: Steven Lee <steven_...@aspeedtech.com> > > > > You didn't reply to the question I asked on the v1 series. > > How useful is this ASPEED_DEV_IOMEM region ? > > > > Sorry for not replying to your question about this patch in the v1 series > earlier. > Somehow our mail server mistakenly flagged that particular message as spam, > so I missed it initially. > > Regarding the ASPEED_DEV_IOMEM region, I checked the datasheet, and > you're right, no devices are mapping registers in this window. > Since it's unused, there's no need to map it in an unimplemented region. I > will > drop this patch in v3 patch series. >
I’d like to revise my previous statement regarding the removal of the ASPEED_DEV_IOMEM region. After further testing, I discovered that either the OP-TEE firmware or u-boot in our AST27xx image performs accesses at address 0x400000. If we remove the unimplemented region mapping for ASPEED_DEV_IOMEM, the firmware hangs during early boot. Although I haven’t yet had time to fully investigate the OP-TEE firmware behavior, I believe it’s safer to keep the unimplemented region for now. This will help prevent similar hangs if other firmware components access that memory range unexpectedly. So instead of dropping the patch in the v3 series, I plan to keep the ASPEED_DEV_IOMEM mapping as a safeguard. Please let me know if this approach looks acceptable to you, or if you have any concerns or suggestions. Best regards, Steven
