1. 19 Sep, 2019 1 commit
    • Bruno Martins's avatar
      BoardConfigQcom: Fix setting UM4.9 and UM4.14 specific flags · 9cfbef4d
      Bruno Martins authored
      Calling is-board-platform-in-list from this makefile was not
      returning the desirable output, thus resulting in a failure
      to meet the conditions for the UM4.9 and UM4.14 family platforms.
      
      Due to the fact that this makefile is included in a very early
      stage in the build process, the QCOM macros are not defined.
      Simply use standard macros like in rest of the makefile.
      
      Change-Id: Iad889882f94167f1bc1761ddd549dac9dcdee3ba
      9cfbef4d
  2. 11 Aug, 2019 1 commit
    • jhenrique09's avatar
      vendor: Add qcom platform type to soongs vars · 97cb87c8
      jhenrique09 authored
      Required for new commits on frameworks/native
      
      * Fix lag during screen recording on some platforms
      * Fix screen flickering after disconnecting from Android Auto on some platforms
      
      Change-Id: Ia0ed0bbfda44fb5ccb184ace854ec1bf9a7d819a
      97cb87c8
  3. 20 Jul, 2019 1 commit
    • Rashed Abdel-Tawab's avatar
      qcom: Add UM 4.14 platforms · 05aded86
      Rashed Abdel-Tawab authored
      * Note: msmnile is treated like msmnile because unlike other Qualcomm
        codenames msmnile does not expand to 8150.
      
      Change-Id: If246c0ec06de22097d369c17ce48aa1270bab19c
      05aded86
  4. 27 Jun, 2019 1 commit
  5. 25 Jun, 2019 2 commits
    • Ethan Chen's avatar
      build: Reorganize inclusion of QCOM macros · 66ce59c8
      Ethan Chen authored
      * 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
      66ce59c8
    • Ethan Chen's avatar
      build: Use ifeq/else ifeq/else construction in board config · b7b49cc0
      Ethan Chen authored
      * Instead of nesting ifeq/else/ifeq/else/endif/endif construction, make
        allows the more readable ifeq/else ifeq/else/endif construction. Use it
        instead.
      
      Change-Id: Ifd2635929799db593e04a13827f05c97e95487e4
      b7b49cc0
  6. 05 Feb, 2019 1 commit
    • Bruno Martins's avatar
      qcom: Mark some gralloc bits as valid · 9717ee7b
      Bruno Martins authored
       * 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 59009f8a).
         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
      9717ee7b
  7. 03 Sep, 2018 2 commits
    • Rashed Abdel-Tawab's avatar
      qcom: Declare PRODUCT_SOONG_NAMESPACES for HALs · a94cf0c7
      Rashed Abdel-Tawab authored
      HALs are starting to move to blueprint files, which means that pathmap
      ifeqs no longer work. This results in modules with the same name in
      different platform HAL directories. Since these modules aren't used or
      linked anywhere outside the HAL directories and a device's device.mk,
      we can safely use a soong namespace to isolate the different HAL
      directories' blueprints. This defines the PRODUCT_SOONG_NAMESPACES
      make flag so make knows which namespace to look in as well.
      
      Change-Id: I549e6da863465d79b12c7453aa169d5d963afa52
      a94cf0c7
    • Rashed Abdel-Tawab's avatar
      lineage: Move QC board variables earlier · b8ac1425
      Rashed Abdel-Tawab authored
      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
      b8ac1425