On Fri, Jun 16, 2017 at 05:07:44PM -0700, Florian Fainelli wrote: > Now that ARM64 also has a fncpy() implementation, allow selection > SRAM_EXEC for ARM64 as well. > > Signed-off-by: Florian Fainelli <f.fainelli@xxxxxxxxx> > --- > drivers/misc/Kconfig | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/misc/Kconfig b/drivers/misc/Kconfig > index 07bbd4cc1852..ac8779278c0c 100644 > --- a/drivers/misc/Kconfig > +++ b/drivers/misc/Kconfig > @@ -464,7 +464,7 @@ config SRAM > bool "Generic on-chip SRAM driver" > depends on HAS_IOMEM > select GENERIC_ALLOCATOR > - select SRAM_EXEC if ARM > + select SRAM_EXEC if ARM || ARM64 > help > This driver allows you to declare a memory region to be managed by > the genalloc API. It is supposed to be used for small on-chip SRAM As stated in another thread [1], NAK to this patch. Currently there are no users of this interface that we wish to enable for arm64, and this is liable to be abused to add platform-specific stuff that we expect to live in PSCI or other secure FW. Until we have a user that does not fall into that bucket, I see no reason to enable this for arm64. Thanks, Mark. [1] http://lists.infradead.org/pipermail/linux-arm-kernel/2017-June/516161.html -- 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
