Joel Stanley e229a179a5 hw: aspeed_gpio: Fix memory size ... The macro used to calculate the maximum memory size of the MMIO region had a mistake, causing all GPIO models to create a mapping of 0x9D8. The intent was to have it be 0x9D8 - 0x800. This extra size doesn't matter on ast2400 and ast2500, which have a 4KB region set aside for the GPIO controller. On the ast2600 the 3.3V and 1.8V GPIO controllers are 2KB apart, so the regions would overlap. Worse was the 1.8V controller would map over the top of the following peripheral, which happens to be the RTC. The mmio region used by each device is a maximum of 2KB, so avoid the calculations and hard code this as the maximum. Fixes: 36d737ee82 ("hw/gpio: Add in AST2600 specific implementation") Signed-off-by: Joel Stanley <joel@jms.id.au> Reviewed-by: Rashmica Gupta <rashmica.g@gmail.com> Reviewed-by: Cédric Le Goater <clg@kaod.org> Message-id: 20210713065854.134634-2-joel@jms.id.au [PMM: fix autocorrect error in commit message] Signed-off-by: Peter Maydell <peter.maydell@linaro.org>		2021-07-27 11:00:00 +01:00
..
aspeed_gpio.c	hw: aspeed_gpio: Fix memory size	2021-07-27 11:00:00 +01:00
bcm2835_gpio.c
gpio_key.c
gpio_pwr.c
imx_gpio.c
Kconfig
max7310.c
meson.build
mpc8xxx.c
npcm7xx_gpio.c
nrf51_gpio.c
omap_gpio.c
pl061.c	hw/gpio/pl061: Document a shortcoming in our implementation	2021-07-09 16:09:12 +01:00
sifive_gpio.c
trace-events
trace.h
zaurus.c