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)
50 lines
1.8 KiB
Makefile
50 lines
1.8 KiB
Makefile
ifeq ($(CONFIG_MEDIATEK_SOLUTION),y)
|
|
MTK_PLATFORM := $(subst ",,$(CONFIG_MTK_PLATFORM))
|
|
ccflags-y += -I$(srctree)/drivers/mmc/core
|
|
ccflags-y += -I$(srctree)/drivers/misc/mediatek/include
|
|
ccflags-y += -I$(srctree)/drivers/misc/mediatek/include/mt-plat/$(MTK_PLATFORM)/include
|
|
ccflags-y += -I$(srctree)/drivers/misc/mediatek/include/mt-plat
|
|
ccflags-y += -I$(srctree)/drivers/misc/mediatek/base/power/$(MTK_PLATFORM)
|
|
ccflags-y += -I$(srctree)/drivers/misc/mediatek/base/power/include
|
|
ccflags-y += -I$(srctree)/drivers/devfreq
|
|
ccflags-y += -I$(srctree)/drivers/scsi/ufs
|
|
|
|
ccflags-y += -I$(srctree)/drivers/mmc/host/mediatek/ComboA
|
|
ifeq ($(CONFIG_MTK_PLATFORM), "mt6761")
|
|
ccflags-y += -I$(srctree)/drivers/mmc/host/mediatek/ComboA/mt6765
|
|
else
|
|
ccflags-y += -I$(srctree)/drivers/mmc/host/mediatek/ComboA/$(MTK_PLATFORM)
|
|
endif
|
|
ccflags-y += -I$(srctree)/drivers/mmc/host/mediatek/$(MTK_PLATFORM)
|
|
ccflags-y += -I$(srctree)/drivers/mmc/host/mediatek/$(MTK_PLATFORM)/$(MTK_PLATFORM)
|
|
|
|
ifeq ($(CONFIG_TRUSTONIC_TEE_SUPPORT),y)
|
|
include $(srctree)/drivers/misc/mediatek/gud/Makefile.include
|
|
ccflags-y += -I$(srctree)/drivers/mmc/host/mediatek/rpmb/drrpmb/public
|
|
ccflags-y += -I$(srctree)/drivers/mmc/host/mediatek/rpmb/drrpmb_gp/public
|
|
ccflags-y += -I$(srctree)/drivers/mmc/host/mediatek/rpmb/tlrpmb/public
|
|
endif
|
|
|
|
#
|
|
# Attention:
|
|
# Enabling/using CFG_RPMB_KEY_PROGRAMED_IN_KERNEL means accepting the
|
|
# risk of revealing key in
|
|
# Linux Kernel. Mediatek won't take the responsibility for loss incurred
|
|
# by the key revealing.
|
|
#
|
|
#ccflags-y += -DCFG_RPMB_KEY_PROGRAMED_IN_KERNEL
|
|
|
|
ifeq ($(CONFIG_MTK_HW_FDE_AES),y)
|
|
ccflags-y += -I$(srctree)/drivers/misc/mediatek/fde_aes/$(MTK_PLATFORM)
|
|
endif
|
|
|
|
obj-$(CONFIG_RPMB) += rpmb-mtk.o
|
|
endif
|
|
|
|
obj-$(CONFIG_RPMB) += rpmb.o
|
|
rpmb-objs += core.o
|
|
rpmb-$(CONFIG_RPMB_INTF_DEV) += cdev.o
|
|
obj-$(CONFIG_RPMB_SIM) += rpmb_sim.o
|
|
|
|
ccflags-y += -D__CHECK_ENDIAN__
|