Hi Weijie,
> I have a better example for reference:
> arch/mips/mach-mtmips
>
> ARCH_MTMIPS is defined for the entire MediaTek MIPS platform, same as
> ARCH_MEDIATEK.
>
> The mtmips then defined its SoC families:
> SOC_MT7620, SOC_MT7621 and SOC_MT7628
>
> Each SoC has its own folder and Kconfig,
The current MediaTek Kconfig layout prevents the addition of new board
targets that require the existing SoC drivers.
By making the SoC drivers depend on new CONFIG_MT variables, it
becomes possible to select these drivers when adding new boards to the
board selection list. The existing TARGET
Hi Leith,
I have a better example for reference:
arch/mips/mach-mtmips
ARCH_MTMIPS is defined for the entire MediaTek MIPS platform, same as
ARCH_MEDIATEK.
The mtmips then defined its SoC families:
SOC_MT7620, SOC_MT7621 and SOC_MT7628
Each SoC has its own folder and Kconfig, e.g.:
arch/mips/ma
3 matches
Mail list logo
