From 4891cc866583532ee3dcb1a5ad5b81670eb0743d Mon Sep 17 00:00:00 2001 From: Julius Werner Date: Thu, 25 Aug 2016 22:37:38 -0700 Subject: [PATCH] rockchip/rk3399: Remove CONFIG_ARM64_A53_ERRATUM_843419 As far as I know, the Cortex-A53 cores in RK3399 are of a newer revision that is not affected by ARM erratum 843419. If it was, the workaround would also need to be enabled in libpayload and Chrome OS userspace, which it currently isn't. I assume this was just incorrectly copied over from another SoC and we can safely remove it. BRANCH=None BUG=chrome-os-partner:56700 TEST=Booted Kevin. Change-Id: Iadb57428f8727ce0e563204723644e2c79e3007c Signed-off-by: Julius Werner Reviewed-on: https://chromium-review.googlesource.com/376363 Commit-Queue: Douglas Anderson Reviewed-by: Douglas Anderson --- src/soc/rockchip/rk3399/Kconfig | 1 - 1 file changed, 1 deletion(-) diff --git a/src/soc/rockchip/rk3399/Kconfig b/src/soc/rockchip/rk3399/Kconfig index 1eaa87019e..b4017c8856 100644 --- a/src/soc/rockchip/rk3399/Kconfig +++ b/src/soc/rockchip/rk3399/Kconfig @@ -5,7 +5,6 @@ config SOC_ROCKCHIP_RK3399 select ARCH_RAMSTAGE_ARMV8_64 select ARCH_ROMSTAGE_ARMV8_64 select ARCH_VERSTAGE_ARMV8_64 - select ARM64_A53_ERRATUM_843419 select ARM64_USE_ARM_TRUSTED_FIRMWARE select BOOTBLOCK_CONSOLE select DRIVERS_UART_8250MEM_32