summaryrefslogtreecommitdiffstats
path: root/arch/arm/mach-s3c64xx/mach-crag6410-module.c
diff options
context:
space:
mode:
authorArnd Bergmann <arnd@arndb.de>2015-02-27 21:54:18 +0100
committerArnd Bergmann <arnd@arndb.de>2015-12-01 21:50:24 +0100
commit0f20e456bd0542b7bf8cae8f553142405a8ab430 (patch)
tree64465e33fa89ab9c84fa0eb7b4dd063e33d8e633 /arch/arm/mach-s3c64xx/mach-crag6410-module.c
parentdf0cc2d1e15f739a428f630feb62ce6f040a4e19 (diff)
downloadtalos-op-linux-0f20e456bd0542b7bf8cae8f553142405a8ab430.tar.gz
talos-op-linux-0f20e456bd0542b7bf8cae8f553142405a8ab430.zip
gpio: samsung: move gpio-samsung driver back to platform code
The gpio-samsung driver is special in the sense that it interacts directly in multiple ways with the legacy platform code for the s3c24xx and s3c64xx platforms. In contrast, all devicetree based machines for Samsung, including the ones on those two SoC families use a different driver. The header files that define the interface between the platform code and the gpio driver are not visible when building a kernel for ARCH_MULTIPLATFORM, which prevents us from turning on this option for s3c64xx. To work around this, we now move the driver back into platform code, from where it was originally moved to as part of commit 1b39d5f2cc5c28 ("gpio/samsung: gpio-samsung.c to support Samsung GPIOs"). The long-term plan for this driver would be to remove it entirely, after all Samsung machines have been converted over to boot from DT, but there is currently no timeline for when that might happen. Signed-off-by: Arnd Bergmann <arnd@arndb.de> Reviewed-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Diffstat (limited to 'arch/arm/mach-s3c64xx/mach-crag6410-module.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud