As of now, if you want to use the eSPI interface, you must define both CONFIG_ESPI and CONFIG_LPC. CONFIG_LPC guards the actually lpc interface and much of the shared host communication code that is generic to both LPC and eSPI.
- We should create a new config option: CONFIG_HOSTCMD_x86 that will guard the code that is generic to both LPC and eSPI.
- We should rename CONFIG_LPC to CONFIG_HOSTCMD_LPC
- We should rename CONFIG_ESPI to CONFIG_HOSTCMD_ESPI
- Automatically define CONFIG_HOSTCMD_x86 if either the lpc or espi config is present
- Produce a build error if both lpc and espi config options are both defined
- Rename any lpc.c files to better reflect what is provides
Comment 1 by jettrink@chromium.org
, Mar 26 2018