From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Rutland Subject: Re: [PATCH v3 0/4] Generalize fncpy availability Date: Mon, 19 Jun 2017 13:24:44 +0100 Message-ID: <20170619122444.GJ10246@leverpostej> References: <20170617000744.22158-1-f.fainelli@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20170617000744.22158-1-f.fainelli@gmail.com> Sender: linux-arch-owner@vger.kernel.org To: Florian Fainelli Cc: linux-arm-kernel@lists.infradead.org, "open list:GENERIC INCLUDE/ASM HEADER FILES" , Arnd Bergmann , Dave Gerlach , Tony Lindgren , Catalin Marinas , Will Deacon , Russell King , open list , bcm-kernel-feedback-list@broadcom.com, Greg Kroah-Hartman , Alexandre Belloni , linux-omap@vger.kernel.org, Shawn Guo , Keerthy J List-Id: linux-omap@vger.kernel.org On Fri, Jun 16, 2017 at 05:07:40PM -0700, Florian Fainelli wrote: > Hi all, Hi Florian, > This patch series makes ARM's fncpy() implementation more generic (dropping the > Thumb-specifics) and available in an asm-generic header file. > > Tested on a Broadcom ARM64 STB platform with code that is written to SRAM. > > Changes in v3 (thanks Doug!): > - correct include guard names in asm-generic/fncpy.h to __ASM_FNCPY_H > - utilize Kbuild to provide the fncpy.h header on ARM64 > > Changes in v2: > - leave the ARM implementation where it is > - make the generic truly generic (no) > > This is helpful in making SoC-specific power management code become true drivers > that can be shared between different architectures. Could you elaborate on what this is needed for? My understanding was that on 32-bit, this was to handle idle / suspend cases, whereas for arm64 that should be handled by PSCI. what exactly do you intend to use this for? Thanks, Mark.