On Mon, Jun 26, 2017 at 03:32:42PM -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> Sorr,y but I must NAK this patch. As mentioned on prior threads regarding fncpy, I do not think it makes sense to enable this for arm64. The only use-cases that have been described so far for this are power-management stuff that should live in PSCI or other secure FW, and have no place in the kernel on arm64. There are no other users of this functionality, and until there are, I see no reason to enable this, and risk a proliferation of unnecessary platform-specific code. It should be possible to #ifdef-ise the relevant callers of this such that they can be built on arm64 without using fncpy or sram_exec functionality. AFAICT, there are no users on arm64 introduced by this series. Thanks, Mark. > --- > 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 > -- > 2.9.3 > -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
