Re: [PATCH v3 4/5] arm64: Add support for Spreadtrum's Sharkl64 Platform in Kconfig and defconfig
From: Arnd Bergmann <hidden>
Date: 2014-11-26 09:01:42
Also in:
linux-arm-kernel, linux-devicetree, linux-serial, lkml
Possibly related (same subject, not in this thread)
- 2014-11-26 · Re: [PATCH v3 4/5] arm64: Add support for Spreadtrum's Sharkl64 Platform in Kconfig and defconfig · Lyra Zhang <zhang.lyra@gmail.com>
- 2014-11-25 · [PATCH v3 4/5] arm64: Add support for Spreadtrum's Sharkl64 Platform in Kconfig and defconfig · Chunyan Zhang <hidden>
- 2014-11-25 · Re: [PATCH v3 4/5] arm64: Add support for Spreadtrum's Sharkl64 Platform in Kconfig and defconfig · Arnd Bergmann <arnd@arndb.de>
On Wednesday 26 November 2014 10:32:35 Lyra Zhang wrote:
For now, we have only one platform(Sharkl64) based on ARM64 been submitted, but we're intending to add support for more our platforms based on ARM64 or ARM32 in the future. There are many common devices on these platforms, such as serial. Our idea would be that if we had a 'menuconfig ARCH_SPRD' in the Kconfig, these common devices only need to depend on ARCH_SPRD in the respective Kconfig, otherwise they may depend on a few Kconfig symbols for every platforms which include these common devices. So, do you think whether we should define a menuconfig(ARCH_SPRD) in the Kconfig for this case ?
It sounds like your other platforms are all related, so one ARCH_SPRD should be enough. If someone wants to build a kernel that is only going to run on a particular machine, they can just turn off all the other drivers they don't want. Arnd