diff options
| author | Subrata Banik <subrata.banik@intel.com> | 2018-01-08 15:28:26 +0530 |
|---|---|---|
| committer | Subrata Banik <subrata.banik@intel.com> | 2018-01-17 02:04:44 +0000 |
| commit | 9e3ba212f34c6d9f2eb7dac8e4651f8ce12ab0c0 (patch) | |
| tree | 61ebc09235481c8964711071b65400ebb81f68f8 /src/soc/intel/skylake/Kconfig | |
| parent | 9b50a57e4343ce77b8ae1aaca5a3866599056456 (diff) | |
soc/intel/cannonlake: Add option to select FSP_CAR
This patch provides an option for non-chrome devices to make use of
FSP-T for performing cache-as-ram initialization. Majority of IOTG users
are using FSP-T for CAR implementation and aren't able to select FSP_CAR
Kconfig from SoC without conflicting with existing CAR config.
TEST=Ensure that both the Chrome platform and non Chrome OS platform
can select either CAR implementation based on Kconfig options
FSP_CAR or CAR_NEM_ENHANCED. By default Chrome platform choose
CAR_NEM_ENHANCED Kconfig and non Chrome platforms choose
FSP_CAR by default.
Change-Id: If565b649fe1c2abdbcf0a740c15db7253c084ae7
Signed-off-by: Subrata Banik <subrata.banik@intel.com>
Reviewed-on: https://review.coreboot.org/23161
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Aaron Durbin <adurbin@chromium.org>
Diffstat (limited to 'src/soc/intel/skylake/Kconfig')
| -rw-r--r-- | src/soc/intel/skylake/Kconfig | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/src/soc/intel/skylake/Kconfig b/src/soc/intel/skylake/Kconfig index 7bb16d20d8..794b8e946f 100644 --- a/src/soc/intel/skylake/Kconfig +++ b/src/soc/intel/skylake/Kconfig @@ -285,27 +285,27 @@ config NHLT_DA7219 choice prompt "Cache-as-ram implementation" - default CAR_NEM_ENHANCED + default USE_SKYLAKE_CAR_NEM_ENHANCED help This option allows you to select how cache-as-ram (CAR) is set up. -config CAR_NEM_ENHANCED +config USE_SKYLAKE_CAR_NEM_ENHANCED bool "Enhanced Non-evict mode" select SOC_INTEL_COMMON_BLOCK_CAR select INTEL_CAR_NEM_ENHANCED help - A current limitation of NEM (Non-Evict mode) is that code and data sizes - are derived from the requirement to not write out any modified cache line. - With NEM, if there is no physical memory behind the cached area, - the modified data will be lost and NEM results will be inconsistent. - ENHANCED NEM guarantees that modified data is always + A current limitation of NEM (Non-Evict mode) is that code and data + sizes are derived from the requirement to not write out any modified + cache line. With NEM, if there is no physical memory behind the + cached area, the modified data will be lost and NEM results will be + inconsistent. ENHANCED NEM guarantees that modified data is always kept in cache while clean data is replaced. config USE_SKYLAKE_FSP_CAR bool "Use FSP CAR" select FSP_CAR help - Use FSP APIs to initialize & tear Down the Cache-As-Ram. + Use FSP APIs to initialize and tear down the Cache-As-Ram. endchoice |