On 09/23/2016 11:23 AM, Tom Rini wrote: > On Fri, Sep 23, 2016 at 04:42:24PM +0000, york sun wrote: >> Tom, >> >> Following this thread, I have different macros to resolve. Please take a >> look at this patch http://patchwork.ozlabs.org/patch/660787/. >> >> It adds CONFIG_SYS_DCSR_RCPM_ADDR and CONFIG_SYS_GIC_ADDR. This kind of >> macros are used across platforms to define the base addresses. All >> existing macros are white-listed. Do we want to make a massive >> conversion to Kconfig, or convert them to a different name space? They >> are not config option, but system implementation. I believe we agreed to >> use CONFIG_SYS_* for this purpose. >> >> I need to convert these two macros before requesting a pull. > > At what system level do these values change? It feels like they should > probably mostly be moved to another namespace with perhaps > CONFIG_SYS_DCSRBAR and CONFIG_SYS_IMMR being expanded a little bit > name-wise and done via Kconfig. >
These two macros are for all current Freescale SoCs. We have a lot registers not used by U-Boot. When new features are added or enabled for an existing SoC, some registers need to be added. Those register base addresses are different on SoCs. Using Kconfig can solve this issue, but requires massive conversion on all existing macros. We may go down this path eventually. But in the interim, I think we can use a different name space to avoid triggering this compiling error. York _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
