+Masahiro, who may know
On 28 September 2016 at 12:57, york sun york.sun@nxp.com wrote:
On 09/27/2016 10:55 AM, Simon Glass wrote:
Hi York,
On 27 September 2016 at 11:39, york sun york.sun@nxp.com wrote:
Guys,
I want to discuss to rearrange the current CONFIG_* macros used by Freescale Layerscape SoCs. We have been encouraged to use CONFIG_SYS_* macros to define hardware setting, and other CONFIG_* macros for user setting. Clearly this has changed. Kconfig options are used for most user settings from now on. I am OK with it. But for existing CONFIG_SYS_* macros, we need a plan to either move them out of CONFIG_* name space, or move some to Kconfig, if that makes sense. Since most our CONFIG_SYS_* macros are cross platforms (including armv7 and armv8), if using Kconfig option, do we add another mach-fsl folder to host the Kconfig, or somewhere else? We also have macros cross ARM and PowerPC. So we either move them out of arch/, or duplicate them for both arch.
If we move them to another name space, for example SYS_FSL_*, do we want to move them out of config.h?
Any suggestion/comment?
I wonder if some of these (the ones that represent actual values rather than enabling functions) can move to device tree, or tables?
While I try to move some options to Kconfig, I have an issue of duplicated names. For example, the MAX_CPUS is used in arch/x86/Kconfig. I know I can put another config with the same name, for example arch/arm/cpu/armv8/fsl-layerscape/Kconfig. The funny thing is when I search for this config option under menuconfig, it shows the location of x86, but showing defined in arch/arm/cpu/armv8/fsl-layerscape/Kconfig. Same thing happens when I try to move an option which is used by both PowerPC and ARM. This is not related to a common driver so I cannot put the option into a driver Kconfig (for example CONFIG_SYS_HAS_SERDES).
Is there a solution for this?
York