On 16.04.20 13:56:58, Geert Uytterhoeven wrote: > Currently the user is asked about enabling support for each and every > vendor-specific erratum, even when support for the specific platform is > not enabled. > > Fix this by adding platform dependencies to the config options > controlling support for vendor-specific errata. > > Note that FUJITSU_ERRATUM_010001 is left untouched, as no config symbol > exists for the Fujitsu A64FX platform. > > Signed-off-by: Geert Uytterhoeven <geert+renesas@xxxxxxxxx> > --- > arch/arm64/Kconfig | 10 ++++++++++ > 1 file changed, 10 insertions(+) > diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig > index 8d33d7fed6d8549b..81f52f0b988e6350 100644 > --- a/arch/arm64/Kconfig > +++ b/arch/arm64/Kconfig > @@ -622,6 +622,8 @@ config ARM64_ERRATUM_1542419 > > If unsure, say Y. > > +if ARCH_THUNDER2 > + > config CAVIUM_ERRATUM_22375 > bool "Cavium erratum 22375, 24313" > default y > @@ -697,6 +699,8 @@ config CAVIUM_TX2_ERRATUM_219 > > If unsure, say Y. > > +endif # ARCH_THUNDER2 For Cavium servers these ARCH_* options are only used to enable some minor (mostly platform) drivers (i2c, spi, gpio, etc.), so the options are not of much use and I better would like to get rid of them completely, which makes us independent and more flexible when enabling or disabling options. In ThunderX* systems there are not many devices that are soc or board specific, most of them are detected using generic methods like pci or acpi. So the situation is rather comparable to x86 systems (there are options based on vendor or core) than to ARM embedded chips. Using the ARCH_* options to control also enablement of cpu errata handling would add a strong dependency here and will make that options a requirement. How about having core/vendor specific submenus that make switching off options easier? Thanks, -Robert
