[RFC] Create arch/Kconfig.nxp

[RFC] Create arch/Kconfig.nxp

[Tom Rini]

[-- Attachment #1: Type: text/plain, Size: 640 bytes --]

Hey all,

As I migrate assorted CONFIG options over to Kconfig, a common problem I
run in to is that between m68k, PowerPC and ARM (both Layerscape and
sometimes i.MX) there are options that fit under more than one
architecture but also don't have a good place to go.  For example, I
just ran in to CONFIG_SYS_FSL_NUM_CC_PLLS which started as PowerPC
specific, but is used still in Layerscape and more of a SoC detail (but
wouldn't make sense in drivers/soc/Kconfig).  I was thinking that
perhaps arch/Kconfig.nxp would be a good starting place to put these
options, but I'm quite open to other suggestions.  Thanks!

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

RE: [RFC] Create arch/Kconfig.nxp

[Peng Fan]

Tom,

I agree to use Kconfig.nxp. thanks for the work.

Thanks,
Peng.

From: Tom Rini <trini@konsulko.com>
Sent: 2022年6月16日 2:00
To: u-boot@lists.denx.de; Priyanka Jain <priyanka.jain@nxp.com>; Peng Fan <peng.fan@nxp.com>; Stefano Babic <sbabic@denx.de>
Subject: [RFC] Create arch/Kconfig.nxp


Hey all,

As I migrate assorted CONFIG options over to Kconfig, a common problem I
run in to is that between m68k, PowerPC and ARM (both Layerscape and
sometimes i.MX) there are options that fit under more than one
architecture but also don't have a good place to go.  For example, I
just ran in to CONFIG_SYS_FSL_NUM_CC_PLLS which started as PowerPC
specific, but is used still in Layerscape and more of a SoC detail (but
wouldn't make sense in drivers/soc/Kconfig).  I was thinking that
perhaps arch/Kconfig.nxp would be a good starting place to put these
options, but I'm quite open to other suggestions.  Thanks!

--
Tom

Re: [RFC] Create arch/Kconfig.nxp

[Stefano Babic]

On 15.06.22 20:00, Tom Rini wrote:
> Hey all,
> 
> As I migrate assorted CONFIG options over to Kconfig, a common problem I
> run in to is that between m68k, PowerPC and ARM (both Layerscape and
> sometimes i.MX) there are options that fit under more than one
> architecture but also don't have a good place to go.  For example, I
> just ran in to CONFIG_SYS_FSL_NUM_CC_PLLS which started as PowerPC
> specific, but is used still in Layerscape and more of a SoC detail (but
> wouldn't make sense in drivers/soc/Kconfig).

That's right, there is IP in common that can be factorized.

>  I was thinking that
> perhaps arch/Kconfig.nxp would be a good starting place to put these
> options, but I'm quite open to other suggestions.

+1

It looks to me a good idea ;-)

Regards,
Stefano


-- 
=====================================================================
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, 82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic@denx.de
=====================================================================