ARCH_VULCAN removal
cover ARCH_VULCAN removal
Another couple of patches to remove more of ARCH_VULCAN platform.
There is still a reference in drivers/gpio/Kconfig for ARCH_VULCAN. I am sending a patch to remove that, and after that we can completely remove ARCH_VULCAN.
JC.
Jayachandran C (2):
arm64: disable Broadcom Vulcan platform
arm64: defconfig: drop ARCH_VULCAN
arch/arm64/Kconfig.platforms | 5 +---- arch/arm64/configs/defconfig | 1 - 2 files changed, 1 insertion(+), 5 deletions(-)
Signature · 1 line
2.7.4
PATCH 1/2 arm64: disable Broadcom Vulcan platform
Disable the option ARCH_VULCAN as a step towards deleting it entirely. There is still a reference in the kernel tree for ARCH_VULCAN, so we have to keep the config option around until that reference is removed.
--- arch/arm64/Kconfig.platforms | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-)
arch/arm64/Kconfig.platforms +1 -4
@@ -225,10 +225,7 @@ config ARCH_VEXPRESS Express). config ARCH_VULCAN - bool "Broadcom Vulcan SOC Family" - select GPIOLIB - help - This enables support for Broadcom Vulcan SoC Family + def_bool n config ARCH_XGENE bool "AppliedMicro X-Gene SOC Family"
Signature · 1 line
2.7.4
PATCH 2/2 arm64: defconfig: drop ARCH_VULCAN
In reply to Jayachandran CARCH_VULCAN (Broadcom Vulcan) has been discontinued and all its dependencies have been moved to ARCH_THUNDER2. It can be dropped from defconfig now.
--- arch/arm64/configs/defconfig | 1 - 1 file changed, 1 deletion(-)
arch/arm64/configs/defconfig +0 -1
@@ -56,7 +56,6 @@ CONFIG_ARCH_THUNDER=y CONFIG_ARCH_THUNDER2=y CONFIG_ARCH_UNIPHIER=y CONFIG_ARCH_VEXPRESS=y -CONFIG_ARCH_VULCAN=y CONFIG_ARCH_XGENE=y CONFIG_ARCH_ZX=y CONFIG_ARCH_ZYNQMP=y
Signature · 1 line
2.7.4
cover ARCH_VULCAN removal
In reply to Jayachandran CQuoted 5 lines · Jayachandran C
Another couple of patches to remove more of
ARCH_VULCANplatform.There is still a reference in
drivers/gpio/KconfigforARCH_VULCAN. I am sending a patch to remove that, and after that we can completely removeARCH_VULCAN.
What happens if ARCH_VULCAN and drivers/gpio/Kconfig still references it? I expected it's just assumed to be 'n' then?
Best regards
Uwe
Signature · 2 lines
Pengutronix e.K. | Uwe Kleine-K?nig | Industrial Linux Solutions | http://www.pengutronix.de/ |
cover ARCH_VULCAN removal
Quoted 9 lines · Uwe Kleine-K?nig
Quoted 5 lines · Jayachandran C
Another couple of patches to remove more of
ARCH_VULCANplatform.There is still a reference in
drivers/gpio/KconfigforARCH_VULCAN. I am sending a patch to remove that, and after that we can completely removeARCH_VULCAN.What happens if
ARCH_VULCANanddrivers/gpio/Kconfigstill references it? I expected it's just assumed to be 'n' then?
Are you talking about this line?
depends on OF_GPIO && (CPU_XLP || ARCH_VULCAN || ARCH_THUNDER2 || COMPILE_TEST)
It will continue to work as long as you enabel ARCH_THUNDER2, which is the "new name" for Vulcan.
(Yes, renames like these are really annoying. We normally don't do them but it's a small one in this case).
-Olof
Olof Johansson
Appliedcover ARCH_VULCAN removal
In reply to Jayachandran CQuoted 6 lines · Jayachandran C
Another couple of patches to remove more of
ARCH_VULCANplatform.There is still a reference in
drivers/gpio/KconfigforARCH_VULCAN. I am sending a patch to remove that, and after that we can completely removeARCH_VULCAN.
Applied to next/arm64 for v4.13.
-Olof