On Thu, Nov 15, 2012 at 03:37:08PM +0000, Rob Herring wrote: > On 11/15/2012 08:37 AM, Catalin Marinas wrote: > > On Thu, Nov 15, 2012 at 02:31:33PM +0000, Rob Herring wrote: > >> Does that work for Versatile Express CA9? It needs ARM_ERRATA_751472. > > > > On VE Linux runs in secure mode, so it's fine. > > WTF? You are contradicting yourself. No, it was just a statement that you can enable this workaround on VE CA9. Didn't realise you were referring to the MULTI_PLATFORM case (it's afternoon and coffee here not that great). > Don't determine secure mode or not, > but apply work-arounds only in secure mode? How does a kernel built to > boot on secure and non-secure chips know that? The requirement would be > that every platform have proper work-arounds setup by the bootloader > regardless of running in secure or non-secure mode. Yes, so for such workarounds that require secure register access just make them depend on !MULTI_PLATFORM. Of course, VE CA9 would be affected since neither the boot loader nor boot monitor touch those bits (yet). But they definitely should as I don't see any other way to support multi-platform, especially when such bits need to be set long before the DT is parsed. -- Catalin -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
