tequilaOS/platform_vendor_tequila
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
platform_vendor_tequila/config/BoardConfigQcom.mk

122 lines
4.6 KiB
Makefile
Raw Normal View History

qcom: Add UM 4.14 platforms * Note: msmnile is treated like msmnile because unlike other Qualcomm codenames msmnile does not expand to 8150. Change-Id: If246c0ec06de22097d369c17ce48aa1270bab19c
2019-05-17 21:03:57 +02:00
# Platform names
qcom: Add UM 4.19 platforms Change-Id: Ida4861b95b0b9748ef3848674b7121010126dd3d
2020-06-25 15:52:52 +02:00
KONA := kona #SM8250
LITO := lito #SM7250
qcom: Add bengal platform Signed-off-by: TheMalachite <eliasgheeraert@gmail.com> Change-Id: Ia9f602a1d6f109554c6462eaa02214c43b9295dd
2021-01-27 00:03:34 +01:00
BENGAL := bengal #SM6115
qcom: Add UM 4.14 platforms * Note: msmnile is treated like msmnile because unlike other Qualcomm codenames msmnile does not expand to 8150. Change-Id: If246c0ec06de22097d369c17ce48aa1270bab19c
2019-05-17 21:03:57 +02:00
MSMNILE := msmnile #SM8150
MSMSTEPPE := sm6150
TRINKET := trinket #SM6125
qcom: Add atoll platform Signed-off-by: TheHitMan7 <krtik.vrma@gmail.com> Change-Id: Idc74d064620649e7423a2fee076da8bd43e1cbd3
2020-05-08 11:03:44 +02:00
ATOLL := atoll #SM6250
qcom: Add UM 4.14 platforms * Note: msmnile is treated like msmnile because unlike other Qualcomm codenames msmnile does not expand to 8150. Change-Id: If246c0ec06de22097d369c17ce48aa1270bab19c
2019-05-17 21:03:57 +02:00
lineage: Move QC board variables earlier These variables are usually set in a device's BoardConfig, setting them in qcom_target is at the very end of the "configuration process" which results in them being unavailable to plenty of other configuration "things" (ex. soong namespaces or soong config). Move them to right after a device's BoardConfig has been found and loaded. Change-Id: Iddd731202d22ed3f8eb010197ce20d3c75a1f40a
2018-08-25 20:10:25 +02:00
B_FAMILY := msm8226 msm8610 msm8974
B64_FAMILY := msm8992 msm8994
BR_FAMILY := msm8909 msm8916
UM_3_18_FAMILY := msm8937 msm8953 msm8996
UM_4_4_FAMILY := msm8998 sdm660
build: Support SDM710 platform Change-Id: I958a6bfd1087f5437f4074e614198bb622d476ce Signed-off-by: Isaac Chen <isaacchen@isaacchen.cn>
2018-10-03 11:59:15 +02:00
UM_4_9_FAMILY := sdm845 sdm710
qcom: Add atoll platform Signed-off-by: TheHitMan7 <krtik.vrma@gmail.com> Change-Id: Idc74d064620649e7423a2fee076da8bd43e1cbd3
2020-05-08 11:03:44 +02:00
UM_4_14_FAMILY := $(MSMNILE) $(MSMSTEPPE) $(TRINKET) $(ATOLL)
qcom: Add bengal platform Signed-off-by: TheMalachite <eliasgheeraert@gmail.com> Change-Id: Ia9f602a1d6f109554c6462eaa02214c43b9295dd
2021-01-27 00:03:34 +01:00
UM_4_19_FAMILY := $(KONA) $(LITO) $(BENGAL)
qcom: Add UM 4.19 platforms Change-Id: Ida4861b95b0b9748ef3848674b7121010126dd3d
2020-06-25 15:52:52 +02:00
UM_PLATFORMS := $(UM_3_18_FAMILY) $(UM_4_4_FAMILY) $(UM_4_9_FAMILY) $(UM_4_14_FAMILY) $(UM_4_19_FAMILY)
lineage: Commonize display_intf_headers for QSSI supported platforms Change-Id: I7224c10295c4123222d81b92f7829502e3cc2d61
2021-01-05 18:04:14 +01:00
QSSI_SUPPORTED_PLATFORMS := $(UM_4_9_FAMILY) $(UM_4_14_FAMILY) $(UM_4_19_FAMILY)
lineage: Move QC board variables earlier These variables are usually set in a device's BoardConfig, setting them in qcom_target is at the very end of the "configuration process" which results in them being unavailable to plenty of other configuration "things" (ex. soong namespaces or soong config). Move them to right after a device's BoardConfig has been found and loaded. Change-Id: Iddd731202d22ed3f8eb010197ce20d3c75a1f40a
2018-08-25 20:10:25 +02:00
BOARD_USES_ADRENO := true
# UM platforms no longer need this set on O+
build: Reorganize inclusion of QCOM macros * There's actually not a whole lot QC-specific about these macros, make them available at definition.mk inclusion time rather than relying on BoardConfig to include them. * Don't create a dependency on QCOM macros from a makefile that is included very early in the build process. Change-Id: I3dcaf0e068ca44732cfe58f69384621781ddda67
2019-06-22 22:30:38 +02:00
ifneq ($(filter $(B_FAMILY) $(B64_FAMILY) $(BR_FAMILY),$(TARGET_BOARD_PLATFORM)),)
lineage: Move QC board variables earlier These variables are usually set in a device's BoardConfig, setting them in qcom_target is at the very end of the "configuration process" which results in them being unavailable to plenty of other configuration "things" (ex. soong namespaces or soong config). Move them to right after a device's BoardConfig has been found and loaded. Change-Id: Iddd731202d22ed3f8eb010197ce20d3c75a1f40a
2018-08-25 20:10:25 +02:00
TARGET_USES_QCOM_BSP := true
endif
# Tell HALs that we're compiling an AOSP build with an in-line kernel
TARGET_COMPILE_WITH_MSM_KERNEL := true
ifneq ($(filter msm7x27a msm7x30 msm8660 msm8960,$(TARGET_BOARD_PLATFORM)),)
TARGET_USES_QCOM_BSP_LEGACY := true
# Enable legacy audio functions
ifeq ($(BOARD_USES_LEGACY_ALSA_AUDIO),true)
USE_CUSTOM_AUDIO_POLICY := 1
endif
endif
# Enable media extensions
TARGET_USES_MEDIA_EXTENSIONS := true
# Allow building audio encoders
TARGET_USES_QCOM_MM_AUDIO := true
# Enable color metadata for every UM platform
build: Reorganize inclusion of QCOM macros * There's actually not a whole lot QC-specific about these macros, make them available at definition.mk inclusion time rather than relying on BoardConfig to include them. * Don't create a dependency on QCOM macros from a makefile that is included very early in the build process. Change-Id: I3dcaf0e068ca44732cfe58f69384621781ddda67
2019-06-22 22:30:38 +02:00
ifneq ($(filter $(UM_PLATFORMS),$(TARGET_BOARD_PLATFORM)),)
lineage: Move QC board variables earlier These variables are usually set in a device's BoardConfig, setting them in qcom_target is at the very end of the "configuration process" which results in them being unavailable to plenty of other configuration "things" (ex. soong namespaces or soong config). Move them to right after a device's BoardConfig has been found and loaded. Change-Id: Iddd731202d22ed3f8eb010197ce20d3c75a1f40a
2018-08-25 20:10:25 +02:00
TARGET_USES_COLOR_METADATA := true
endif
# Enable DRM PP driver on UM platforms that support it
qcom: Add UM 4.19 platforms Change-Id: Ida4861b95b0b9748ef3848674b7121010126dd3d
2020-06-25 15:52:52 +02:00
ifneq ($(filter $(UM_4_9_FAMILY) $(UM_4_14_FAMILY) $(UM_4_19_FAMILY),$(TARGET_BOARD_PLATFORM)),)
lineage: Move QC board variables earlier These variables are usually set in a device's BoardConfig, setting them in qcom_target is at the very end of the "configuration process" which results in them being unavailable to plenty of other configuration "things" (ex. soong namespaces or soong config). Move them to right after a device's BoardConfig has been found and loaded. Change-Id: Iddd731202d22ed3f8eb010197ce20d3c75a1f40a
2018-08-25 20:10:25 +02:00
TARGET_USES_DRM_PP := true
endif
config: Mark more gralloc bits as valid * Mimic the behavior of https://source.codeaurora.org/quic/la/platform/frameworks/native/commit/?h=LA.UM.8.6.r1-01900-89xx.0&id=002db77e0d84893d498f5a9544ec7941158c71e8. Change-Id: Id87564acde3d05f10a266c580f6931d444c91b9e
2019-09-28 11:23:16 +02:00
# Mark GRALLOC_USAGE_HW_2D, GRALLOC_USAGE_EXTERNAL_DISP and GRALLOC_USAGE_PRIVATE_WFD as valid gralloc bits
qcom: Mark some gralloc bits as valid * Add GRALLOC_USAGE_PRIVATE_WFD as valid gralloc bits for all the platforms and GRALLOC_USAGE_PRIVATE_10BIT_TP only for the UM 4.9-based platforms. Both are defined in the respective display HALs (in gralloc/gralloc_priv.h) being the latter only available for sdm845. * This results in the same as applying https://goo.gl/SR7sFY, but it's preferable since it makes use of our own method of extending the valid gralloc 1.0 usage bits (see commit 59009f8). TARGET_ADDITIONAL_GRALLOC_10_USAGE_BITS is extended here on purpose and as a bitwise OR of all the values in order not to clear what might have been set in the device trees. Change-Id: I5536f341e75088cc72ac369065011388f0a6d3f1
2018-12-28 22:34:03 +01:00
TARGET_ADDITIONAL_GRALLOC_10_USAGE_BITS ?= 0
config: Mark more gralloc bits as valid * Mimic the behavior of https://source.codeaurora.org/quic/la/platform/frameworks/native/commit/?h=LA.UM.8.6.r1-01900-89xx.0&id=002db77e0d84893d498f5a9544ec7941158c71e8. Change-Id: Id87564acde3d05f10a266c580f6931d444c91b9e
2019-09-28 11:23:16 +02:00
TARGET_ADDITIONAL_GRALLOC_10_USAGE_BITS += | (1 << 10)
TARGET_ADDITIONAL_GRALLOC_10_USAGE_BITS += | (1 << 13)
qcom: Mark some gralloc bits as valid * Add GRALLOC_USAGE_PRIVATE_WFD as valid gralloc bits for all the platforms and GRALLOC_USAGE_PRIVATE_10BIT_TP only for the UM 4.9-based platforms. Both are defined in the respective display HALs (in gralloc/gralloc_priv.h) being the latter only available for sdm845. * This results in the same as applying https://goo.gl/SR7sFY, but it's preferable since it makes use of our own method of extending the valid gralloc 1.0 usage bits (see commit 59009f8). TARGET_ADDITIONAL_GRALLOC_10_USAGE_BITS is extended here on purpose and as a bitwise OR of all the values in order not to clear what might have been set in the device trees. Change-Id: I5536f341e75088cc72ac369065011388f0a6d3f1
2018-12-28 22:34:03 +01:00
TARGET_ADDITIONAL_GRALLOC_10_USAGE_BITS += | (1 << 21)
config: Mark more gralloc bits as valid * Mimic the behavior of https://source.codeaurora.org/quic/la/platform/frameworks/native/commit/?h=LA.UM.8.6.r1-01900-89xx.0&id=002db77e0d84893d498f5a9544ec7941158c71e8. Change-Id: Id87564acde3d05f10a266c580f6931d444c91b9e
2019-09-28 11:23:16 +02:00
# Mark GRALLOC_USAGE_PRIVATE_HEIF_VIDEO as valid gralloc bits on UM platforms that support it
qcom: Add UM 4.19 platforms Change-Id: Ida4861b95b0b9748ef3848674b7121010126dd3d
2020-06-25 15:52:52 +02:00
ifneq ($(filter $(UM_4_9_FAMILY) $(UM_4_14_FAMILY) $(UM_4_19_FAMILY),$(TARGET_BOARD_PLATFORM)),)
qcom: Mark some gralloc bits as valid * Add GRALLOC_USAGE_PRIVATE_WFD as valid gralloc bits for all the platforms and GRALLOC_USAGE_PRIVATE_10BIT_TP only for the UM 4.9-based platforms. Both are defined in the respective display HALs (in gralloc/gralloc_priv.h) being the latter only available for sdm845. * This results in the same as applying https://goo.gl/SR7sFY, but it's preferable since it makes use of our own method of extending the valid gralloc 1.0 usage bits (see commit 59009f8). TARGET_ADDITIONAL_GRALLOC_10_USAGE_BITS is extended here on purpose and as a bitwise OR of all the values in order not to clear what might have been set in the device trees. Change-Id: I5536f341e75088cc72ac369065011388f0a6d3f1
2018-12-28 22:34:03 +01:00
TARGET_ADDITIONAL_GRALLOC_10_USAGE_BITS += | (1 << 27)
endif
lineage: Move QC board variables earlier These variables are usually set in a device's BoardConfig, setting them in qcom_target is at the very end of the "configuration process" which results in them being unavailable to plenty of other configuration "things" (ex. soong namespaces or soong config). Move them to right after a device's BoardConfig has been found and loaded. Change-Id: Iddd731202d22ed3f8eb010197ce20d3c75a1f40a
2018-08-25 20:10:25 +02:00
# List of targets that use master side content protection
qcom: Add UM 4.19 platforms Change-Id: Ida4861b95b0b9748ef3848674b7121010126dd3d
2020-06-25 15:52:52 +02:00
MASTER_SIDE_CP_TARGET_LIST := msm8996 $(UM_4_4_FAMILY) $(UM_4_9_FAMILY) $(UM_4_14_FAMILY) $(UM_4_19_FAMILY)
lineage: Move QC board variables earlier These variables are usually set in a device's BoardConfig, setting them in qcom_target is at the very end of the "configuration process" which results in them being unavailable to plenty of other configuration "things" (ex. soong namespaces or soong config). Move them to right after a device's BoardConfig has been found and loaded. Change-Id: Iddd731202d22ed3f8eb010197ce20d3c75a1f40a
2018-08-25 20:10:25 +02:00
build: Reorganize inclusion of QCOM macros * There's actually not a whole lot QC-specific about these macros, make them available at definition.mk inclusion time rather than relying on BoardConfig to include them. * Don't create a dependency on QCOM macros from a makefile that is included very early in the build process. Change-Id: I3dcaf0e068ca44732cfe58f69384621781ddda67
2019-06-22 22:30:38 +02:00
ifneq ($(filter $(B_FAMILY),$(TARGET_BOARD_PLATFORM)),)
lineage: Move QC board variables earlier These variables are usually set in a device's BoardConfig, setting them in qcom_target is at the very end of the "configuration process" which results in them being unavailable to plenty of other configuration "things" (ex. soong namespaces or soong config). Move them to right after a device's BoardConfig has been found and loaded. Change-Id: Iddd731202d22ed3f8eb010197ce20d3c75a1f40a
2018-08-25 20:10:25 +02:00
MSM_VIDC_TARGET_LIST := $(B_FAMILY)
QCOM_HARDWARE_VARIANT := msm8974
build: Reorganize inclusion of QCOM macros * There's actually not a whole lot QC-specific about these macros, make them available at definition.mk inclusion time rather than relying on BoardConfig to include them. * Don't create a dependency on QCOM macros from a makefile that is included very early in the build process. Change-Id: I3dcaf0e068ca44732cfe58f69384621781ddda67
2019-06-22 22:30:38 +02:00
else ifneq ($(filter $(B64_FAMILY),$(TARGET_BOARD_PLATFORM)),)
lineage: Move QC board variables earlier These variables are usually set in a device's BoardConfig, setting them in qcom_target is at the very end of the "configuration process" which results in them being unavailable to plenty of other configuration "things" (ex. soong namespaces or soong config). Move them to right after a device's BoardConfig has been found and loaded. Change-Id: Iddd731202d22ed3f8eb010197ce20d3c75a1f40a
2018-08-25 20:10:25 +02:00
MSM_VIDC_TARGET_LIST := $(B64_FAMILY)
QCOM_HARDWARE_VARIANT := msm8994
build: Reorganize inclusion of QCOM macros * There's actually not a whole lot QC-specific about these macros, make them available at definition.mk inclusion time rather than relying on BoardConfig to include them. * Don't create a dependency on QCOM macros from a makefile that is included very early in the build process. Change-Id: I3dcaf0e068ca44732cfe58f69384621781ddda67
2019-06-22 22:30:38 +02:00
else ifneq ($(filter $(BR_FAMILY),$(TARGET_BOARD_PLATFORM)),)
lineage: Move QC board variables earlier These variables are usually set in a device's BoardConfig, setting them in qcom_target is at the very end of the "configuration process" which results in them being unavailable to plenty of other configuration "things" (ex. soong namespaces or soong config). Move them to right after a device's BoardConfig has been found and loaded. Change-Id: Iddd731202d22ed3f8eb010197ce20d3c75a1f40a
2018-08-25 20:10:25 +02:00
MSM_VIDC_TARGET_LIST := $(BR_FAMILY)
QCOM_HARDWARE_VARIANT := msm8916
build: Reorganize inclusion of QCOM macros * There's actually not a whole lot QC-specific about these macros, make them available at definition.mk inclusion time rather than relying on BoardConfig to include them. * Don't create a dependency on QCOM macros from a makefile that is included very early in the build process. Change-Id: I3dcaf0e068ca44732cfe58f69384621781ddda67
2019-06-22 22:30:38 +02:00
else ifneq ($(filter $(UM_3_18_FAMILY),$(TARGET_BOARD_PLATFORM)),)
lineage: Move QC board variables earlier These variables are usually set in a device's BoardConfig, setting them in qcom_target is at the very end of the "configuration process" which results in them being unavailable to plenty of other configuration "things" (ex. soong namespaces or soong config). Move them to right after a device's BoardConfig has been found and loaded. Change-Id: Iddd731202d22ed3f8eb010197ce20d3c75a1f40a
2018-08-25 20:10:25 +02:00
MSM_VIDC_TARGET_LIST := $(UM_3_18_FAMILY)
QCOM_HARDWARE_VARIANT := msm8996
build: Reorganize inclusion of QCOM macros * There's actually not a whole lot QC-specific about these macros, make them available at definition.mk inclusion time rather than relying on BoardConfig to include them. * Don't create a dependency on QCOM macros from a makefile that is included very early in the build process. Change-Id: I3dcaf0e068ca44732cfe58f69384621781ddda67
2019-06-22 22:30:38 +02:00
else ifneq ($(filter $(UM_4_4_FAMILY),$(TARGET_BOARD_PLATFORM)),)
lineage: Move QC board variables earlier These variables are usually set in a device's BoardConfig, setting them in qcom_target is at the very end of the "configuration process" which results in them being unavailable to plenty of other configuration "things" (ex. soong namespaces or soong config). Move them to right after a device's BoardConfig has been found and loaded. Change-Id: Iddd731202d22ed3f8eb010197ce20d3c75a1f40a
2018-08-25 20:10:25 +02:00
MSM_VIDC_TARGET_LIST := $(UM_4_4_FAMILY)
QCOM_HARDWARE_VARIANT := msm8998
build: Reorganize inclusion of QCOM macros * There's actually not a whole lot QC-specific about these macros, make them available at definition.mk inclusion time rather than relying on BoardConfig to include them. * Don't create a dependency on QCOM macros from a makefile that is included very early in the build process. Change-Id: I3dcaf0e068ca44732cfe58f69384621781ddda67
2019-06-22 22:30:38 +02:00
else ifneq ($(filter $(UM_4_9_FAMILY),$(TARGET_BOARD_PLATFORM)),)
lineage: Move QC board variables earlier These variables are usually set in a device's BoardConfig, setting them in qcom_target is at the very end of the "configuration process" which results in them being unavailable to plenty of other configuration "things" (ex. soong namespaces or soong config). Move them to right after a device's BoardConfig has been found and loaded. Change-Id: Iddd731202d22ed3f8eb010197ce20d3c75a1f40a
2018-08-25 20:10:25 +02:00
MSM_VIDC_TARGET_LIST := $(UM_4_9_FAMILY)
QCOM_HARDWARE_VARIANT := sdm845
qcom: Add UM 4.14 platforms * Note: msmnile is treated like msmnile because unlike other Qualcomm codenames msmnile does not expand to 8150. Change-Id: If246c0ec06de22097d369c17ce48aa1270bab19c
2019-05-17 21:03:57 +02:00
else ifneq ($(filter $(UM_4_14_FAMILY),$(TARGET_BOARD_PLATFORM)),)
MSM_VIDC_TARGET_LIST := $(UM_4_14_FAMILY)
QCOM_HARDWARE_VARIANT := sm8150
qcom: Add UM 4.19 platforms Change-Id: Ida4861b95b0b9748ef3848674b7121010126dd3d
2020-06-25 15:52:52 +02:00
else ifneq ($(filter $(UM_4_19_FAMILY),$(TARGET_BOARD_PLATFORM)),)
MSM_VIDC_TARGET_LIST := $(UM_4_19_FAMILY)
QCOM_HARDWARE_VARIANT := sm8250
lineage: Move QC board variables earlier These variables are usually set in a device's BoardConfig, setting them in qcom_target is at the very end of the "configuration process" which results in them being unavailable to plenty of other configuration "things" (ex. soong namespaces or soong config). Move them to right after a device's BoardConfig has been found and loaded. Change-Id: Iddd731202d22ed3f8eb010197ce20d3c75a1f40a
2018-08-25 20:10:25 +02:00
else
MSM_VIDC_TARGET_LIST := $(TARGET_BOARD_PLATFORM)
QCOM_HARDWARE_VARIANT := $(TARGET_BOARD_PLATFORM)
endif
BoardConfigQcom: Allow a device to opt-out hardset of PRODUCT_SOONG_NAMESPACES By setting QCOM_SOONG_NAMESPACE in device.mk This will allow a device to specify a device specific branch within hardware/qcom-caf/ or the device tree. Signed-off-by: Andrew Hexen <SyberHexen@gmail.com> Change-Id: I39693a0fb9665129f0810590d389c4cb06cdf8d7
2020-05-12 01:13:13 +02:00
# Allow a device to opt-out hardset of PRODUCT_SOONG_NAMESPACES
QCOM_SOONG_NAMESPACE ?= hardware/qcom-caf/$(QCOM_HARDWARE_VARIANT)
PRODUCT_SOONG_NAMESPACES += $(QCOM_SOONG_NAMESPACE)
lineage: Add data-ipa-cfg-mgr to soong namespace in BoardConfigQcom Before: $ breakfast capricorn && m ipacm FAILED: ninja: unknown target 'ipacm', did you mean 'lpadd'? After: $ breakfast capricorn && m ipacm * happily compiles * Change-Id: Ib68978d4f287dcdea45fc21382af05b1890caca4
2020-10-30 13:32:49 +01:00
lineage: Commonize display_intf_headers for QSSI supported platforms Change-Id: I7224c10295c4123222d81b92f7829502e3cc2d61
2021-01-05 18:04:14 +01:00
# Add display-commonsys-intf to PRODUCT_SOONG_NAMESPACES for QSSI supported platforms
ifneq ($(filter $(QSSI_SUPPORTED_PLATFORMS),$(TARGET_BOARD_PLATFORM)),)
PRODUCT_SOONG_NAMESPACES += vendor/qcom/opensource/commonsys-intf/display
endif
lineage: Add data-ipa-cfg-mgr to soong namespace in BoardConfigQcom Before: $ breakfast capricorn && m ipacm FAILED: ninja: unknown target 'ipacm', did you mean 'lpadd'? After: $ breakfast capricorn && m ipacm * happily compiles * Change-Id: Ib68978d4f287dcdea45fc21382af05b1890caca4
2020-10-30 13:32:49 +01:00
# Add data-ipa-cfg-mgr to PRODUCT_SOONG_NAMESPACES if needed
ifneq ($(USE_DEVICE_SPECIFIC_DATA_IPA_CFG_MGR),true)
PRODUCT_SOONG_NAMESPACES += vendor/qcom/opensource/data-ipa-cfg-mgr
endif
config: Setup soong namespaces for TARGET_USE_QTI_BT_STACK To opt-in for QTI BT addons, enable TARGET_USE_QTI_BT_STACK in BoardConfig.mk Reference: [https://github.com/LineageOS/android_vendor_qcom_opensource_bluetooth-commonsys-intf/blob/lineage-18.0/bt-system-opensource-product.mk] Change-Id: I6bf3e1dda6fe5dc66f6fafdb32a1daecb9616c84
2020-09-19 02:44:33 +02:00
config: Add dataservices to PRODUCT_SOONG_NAMESPACES if needed The mk files in vendor/qcom/opensource/dataservices were converted to bp, so this is needed to avoid duplicate module build errors on devices that use a different dataservices lib. Change-Id: Ic5c1ad77342c045253cfd093c76706862ed6fd0e
2020-12-30 20:58:08 +01:00
# Add dataservices to PRODUCT_SOONG_NAMESPACES if needed
ifneq ($(USE_DEVICE_SPECIFIC_DATASERVICES),true)
PRODUCT_SOONG_NAMESPACES += vendor/qcom/opensource/dataservices
endif
config: Setup soong namespaces for TARGET_USE_QTI_BT_STACK To opt-in for QTI BT addons, enable TARGET_USE_QTI_BT_STACK in BoardConfig.mk Reference: [https://github.com/LineageOS/android_vendor_qcom_opensource_bluetooth-commonsys-intf/blob/lineage-18.0/bt-system-opensource-product.mk] Change-Id: I6bf3e1dda6fe5dc66f6fafdb32a1daecb9616c84
2020-09-19 02:44:33 +02:00
ifeq ($(TARGET_USE_QTI_BT_STACK),true)
PRODUCT_SOONG_NAMESPACES += \
vendor/qcom/opensource/commonsys/packages/apps/Bluetooth \
vendor/qcom/opensource/commonsys/system/bt/conf
endif #TARGET_USE_QTI_BT_STACK
Reference in a new issue Copy permalink