On Thu, Oct 05, 2017 at 09:16:12PM +0300, Dmitry Osipenko wrote: > On 20.07.2017 03:29, Michał Mirosław wrote: > > Allow secure-only erratas to be used in multiarch kernel. > > > > Signed-off-by: Michał Mirosław <mirq-linux@xxxxxxxxxxxx> > > --- > > arch/arm/Kconfig | 20 ++++++++++++++------ > > 1 file changed, 14 insertions(+), 6 deletions(-) > > > > diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig > > index a208bfe367b5..a1eff866550b 100644 > > --- a/arch/arm/Kconfig > > +++ b/arch/arm/Kconfig > > @@ -696,6 +696,14 @@ config ARCH_MULTI_CPU_AUTO > > > > endmenu > > > > +config ARCH_ASSUME_SECURE_PLATFORM > > + bool "Enable ERRATAs using secure-only registers" > > + default !ARCH_MULTIPLATFORM > > I think default should always be "Yes" and this option shouldn't affect > multiplatform kernels. So a multiplatform kernel wouldn't be an option > for your device. No, that changes the current behaviour. Current behaviour is for the secure-only errata to be disabled when the multi-platform option is enabled, because multi-platform kernels have to be able to run in the non-secure world. Defaulting this option to "yes" means that these errata become visible. I have to wonder why you need this though - your patches seem to be targetting a platform that runs in non-secure world, and enabling these errata would make the kernel non-bootable on your platform. -- RMK's Patch system: http://www.armlinux.org.uk/developer/patches/ FTTC broadband for 0.8mile line in suburbia: sync at 8.8Mbps down 630kbps up According to speedtest.net: 8.21Mbps down 510kbps up -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
