Squashed backup commit (no shallow-clone history issues) of xiaomi-mt6833-dev/kernel_xiaomi_mt6833 (lineage-23.2 branch, upstream commit 9eece662e) plus all fixes applied to get everpal_defconfig building clean against a modern (GCC 15.2.0) toolchain -- see the previous commit message on the lineage-23.2 branch (also in this repo history is not available here since this is a squashed snapshot; full incremental history lives in the local DL380 checkout and the upstream GitHub remote). Upstream: https://github.com/xiaomi-mt6833-dev/kernel_xiaomi_mt6833 (lineage-23.2)
60 lines
1015 B
Plaintext
60 lines
1015 B
Plaintext
# SPDX-License-Identifier: GPL-2.0
|
|
if LANTIQ
|
|
|
|
config SOC_TYPE_XWAY
|
|
bool
|
|
select PINCTRL_XWAY
|
|
default n
|
|
|
|
choice
|
|
prompt "SoC Type"
|
|
default SOC_XWAY
|
|
|
|
config SOC_AMAZON_SE
|
|
bool "Amazon SE"
|
|
select SOC_TYPE_XWAY
|
|
select MFD_SYSCON
|
|
select MFD_CORE
|
|
|
|
config SOC_XWAY
|
|
bool "XWAY"
|
|
select SOC_TYPE_XWAY
|
|
select HW_HAS_PCI
|
|
select MFD_SYSCON
|
|
select MFD_CORE
|
|
|
|
config SOC_FALCON
|
|
bool "FALCON"
|
|
select PINCTRL_FALCON
|
|
|
|
endchoice
|
|
|
|
choice
|
|
prompt "Built-in device tree"
|
|
help
|
|
Legacy bootloaders do not pass a DTB pointer to the kernel, so
|
|
if a "wrapper" is not being used, the kernel will need to include
|
|
a device tree that matches the target board.
|
|
|
|
The builtin DTB will only be used if the firmware does not supply
|
|
a valid DTB.
|
|
|
|
config LANTIQ_DT_NONE
|
|
bool "None"
|
|
|
|
config DT_EASY50712
|
|
bool "Easy50712"
|
|
depends on SOC_XWAY
|
|
select BUILTIN_DTB
|
|
endchoice
|
|
|
|
config PCI_LANTIQ
|
|
bool "PCI Support"
|
|
depends on SOC_XWAY && PCI
|
|
|
|
config XRX200_PHY_FW
|
|
bool "XRX200 PHY firmware loader"
|
|
depends on SOC_XWAY
|
|
|
|
endif
|