851ef96f4e
Chrome EC uses IO ports 0x800 -> 0x9ff to communicate over LPC; however, those ports were not declared as a resource. This had two major downsides: * It allowed the allocator to assign said ports to other devices * It required manually open up an IO window in the LPC bridge. The LPC bridge on many chromeec boards had to be painstakingly adjusted to meet these constraints. The advantage of declaring the resources upfront is that the lpc bridge can now scan its child resources and automatically open up IO windows, as requested by its LPC children devices. Change-Id: I35c4e48dddb7300674d7a9858b590c1f20e3b0e3 Signed-off-by: Alexandru Gagniuc <alexandrux.gagniuc@intel.com> Reviewed-on: https://review.coreboot.org/14585 Reviewed-by: Aaron Durbin <adurbin@chromium.org> Tested-by: build bot (Jenkins) |
||
|---|---|---|
| .. | ||
| acpi | ||
| chip.h | ||
| crosec_proto.c | ||
| ec.c | ||
| ec.h | ||
| ec_commands.h | ||
| ec_i2c.c | ||
| ec_lpc.c | ||
| ec_mec.c | ||
| ec_message.h | ||
| ec_spi.c | ||
| Kconfig | ||
| Makefile.inc | ||
| vboot_storage.c | ||
| vstore.c | ||