ec/google/chromeec/ec_lpc: Declare used IO ports as a resource
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)
This commit is contained in:
parent
3aa34a8167
commit
851ef96f4e
|
@ -59,6 +59,10 @@ int google_chromeec_vstore_info(uint32_t *locked);
|
|||
int google_chromeec_vstore_read(int slot, uint8_t *data);
|
||||
int google_chromeec_vstore_write(int slot, uint8_t *data, size_t size);
|
||||
|
||||
/* MEC uses 0x800/0x804 as register/index pair, thus an 8-byte resource. */
|
||||
#define MEC_EMI_BASE 0x800
|
||||
#define MEC_EMI_SIZE 8
|
||||
|
||||
/* For MEC, access ranges 0x800 thru 0x9ff using EMI interface instead of LPC */
|
||||
#define MEC_EMI_RANGE_START EC_HOST_CMD_REGION0
|
||||
#define MEC_EMI_RANGE_END (EC_LPC_ADDR_MEMMAP + EC_MEMMAP_SIZE)
|
||||
|
|
|
@ -14,6 +14,7 @@
|
|||
*/
|
||||
|
||||
#include <arch/io.h>
|
||||
#include <assert.h>
|
||||
#include <console/console.h>
|
||||
#include <delay.h>
|
||||
#include <device/pnp.h>
|
||||
|
@ -407,9 +408,35 @@ static void lpc_ec_init(struct device *dev)
|
|||
google_chromeec_init();
|
||||
}
|
||||
|
||||
/*
|
||||
* Declare the IO ports that we are using:
|
||||
*
|
||||
* All ECs (not explicitly declared):
|
||||
* 0x60/0x64, 0x62/0x66, 0x80, 0x200->0x207
|
||||
*
|
||||
* mec1322: 0x800->0x807
|
||||
* All others: 0x800->0x9ff
|
||||
*
|
||||
* EC_GOOGLE_CHROMEEC_ACPI_MEMMAP is only used for MEC ECs.
|
||||
*/
|
||||
static void lpc_ec_read_resources(struct device *dev)
|
||||
{
|
||||
/* Nothing, but this function avoids an error on serial console. */
|
||||
unsigned int idx = 0;
|
||||
struct resource * res;
|
||||
|
||||
|
||||
res = new_resource(dev, idx++);
|
||||
if (IS_ENABLED(CONFIG_EC_GOOGLE_CHROMEEC_MEC)) {
|
||||
res->base = MEC_EMI_BASE;
|
||||
res->size = MEC_EMI_SIZE;
|
||||
} else {
|
||||
res->base = EC_HOST_CMD_REGION0;
|
||||
res->size = 2 * EC_HOST_CMD_REGION_SIZE;
|
||||
/* Make sure MEMMAP region follows host cmd region. */
|
||||
assert(res->base + res->size == EC_LPC_ADDR_MEMMAP);
|
||||
res->size += EC_MEMMAP_SIZE;
|
||||
}
|
||||
res->flags = IORESOURCE_IO | IORESOURCE_ASSIGNED | IORESOURCE_FIXED;
|
||||
}
|
||||
|
||||
static void lpc_ec_enable_resources(struct device *dev)
|
||||
|
|
|
@ -32,7 +32,6 @@ enum {
|
|||
};
|
||||
|
||||
/* EMI registers are relative to base */
|
||||
#define MEC_EMI_BASE 0x800
|
||||
#define MEC_EMI_HOST_TO_EC (MEC_EMI_BASE + 0)
|
||||
#define MEC_EMI_EC_TO_HOST (MEC_EMI_BASE + 1)
|
||||
#define MEC_EMI_EC_ADDRESS_B0 (MEC_EMI_BASE + 2)
|
||||
|
|
Loading…
Reference in New Issue