From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] Rearrange CONFIG_* macros
Date: Tue, 27 Sep 2016 13:51:56 -0400 [thread overview]
Message-ID: <20160927175156.GO4884@bill-the-cat> (raw)
In-Reply-To: <AM4PR0401MB1732EB982C2FE598A5A19E0C9ACC0@AM4PR0401MB1732.eurprd04.prod.outlook.com>
On Tue, Sep 27, 2016 at 05:39:55PM +0000, york sun 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?
Well, if something is cross-platform the code is somewhere
cross-platform too, yes? For example, if anything DDR related makes
sense to stay as CONFIG_SYS_FSL_... it could go in to
drivers/ddr/fsl/Kconfig and be visible in both cases. Otherwise
<asm/arch/fsl_ddr.h> and SYS_FSL_... (or whatever makes sense, looking
at the am33xx and mx6 cases, there's no SYS_ type prefix on the defines,
just the IP block names) for the defines.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160927/03e578f9/attachment.sig>
next prev parent reply other threads:[~2016-09-27 17:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-27 17:39 [U-Boot] [RFC] Rearrange CONFIG_* macros york sun
2016-09-27 17:51 ` Tom Rini [this message]
2016-09-27 18:24 ` york sun
2016-09-27 18:40 ` Tom Rini
2016-09-27 17:55 ` Simon Glass
2016-09-27 18:26 ` york sun
2016-09-28 18:57 ` york sun
2016-09-28 19:17 ` Simon Glass
2016-09-29 15:47 ` york sun
2016-09-30 3:59 ` Masahiro Yamada
2016-09-30 4:20 ` york sun
2016-10-01 2:24 ` Tom Rini
2016-10-03 16:35 ` Scott Wood
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160927175156.GO4884@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox