1. 05 Jan, 2022 1 commit
  2. 29 Dec, 2021 4 commits
  3. 22 Dec, 2021 3 commits
  4. 20 Dec, 2021 1 commit
    • Yongqin Liu's avatar
      drm_hwcomposer: support more connector types · cdee4f2b
      Yongqin Liu authored
      
      
      according to the drm_connector_enum_list defined
      in the kernel file drivers/gpu/drm/drm_connector.c
      
      Otherwise for the new connector type, the connector
      name will be "None" to be printed  in the logcat, like this:
          12-13 05:38:06.263   383   383 I hwc-backend: Backend 'generic' for 'None' and driver 'omapdrm' was successfully set
      with this change, it will be fixed with the connector type like this:
          12-13 06:01:57.672   342   342 I hwc-backend: Backend 'generic' for 'DPI-1' and driver 'omapdrm' was successfully set
      
      Also updated the internal() and external() functions
      to make the newly added SPI and USB are valid types
      
      Signed-off-by: Yongqin Liu's avatarYongqin Liu <yongqin.liu@linaro.org>
      cdee4f2b
  5. 13 Dec, 2021 1 commit
    • Roman Stratiienko's avatar
      drm_hwcomposer: Assume premultiplied alpha for CLIENT layer · 720f6522
      Roman Stratiienko authored and John Stultz's avatar John Stultz committed
      On db845c, we have seen an odd behavior with modal dialogs in
      AOSP, where the background which is normally darkened, was
      rendering as black, though it would occasionally flicker to the
      right thing. This cropped up after alpha support on planes
      landed in 5.15, so we assumed it was an edge case issue with the
      dpu1 driver.
      
      But while working on a separate issue seen on x86 hardware:
        drm-hwcomposer/drm-hwcomposer#46
      
      
      
      Roman noticed drm_hwcomposer always sets the blending type to
      NONE for the client layer. Which had gone un-noticed becase he
      didn't have any devices that exposed the NONE type.
      
      Thus Roman implemented this patch, which sets up the client
      blend type to PREMULTIPLIED.
      
      While it did not resolve the x86 issue above, it does resolve
      the incorrect rendering seen on db845c with alpha support
      enabled.
      
      Tested-by: Martin Juecker martin.juecker@gmail.com #Exynos 4412
      Signed-off-by: default avatarRoman Stratiienko <roman.o.stratiienko@globallogic.com>
      Signed-off-by: John Stultz's avatarJohn Stultz <john.stultz@linaro.org>
      Change-Id: I95601c680ca1af0dc9d3b3f102f79f77af081b75
      720f6522
  6. 07 Dec, 2021 1 commit
  7. 06 Dec, 2021 2 commits
  8. 02 Dec, 2021 1 commit
    • Roman Stratiienko's avatar
      drm_hwcomposer: Rework display modes handling · a148f213
      Roman Stratiienko authored
      
      
      Android likes to adapt display output frequency to match window context
      frequency. Unfortunately platform code has some limitations, therefore
      hwcomposer HAL should be careful with reporting supported display modes.
      
      Known platform limitations:
      1: Framework doesn't distinguish between interlaced/progressive modes.
      2. Framework will not switch display frequency in case margin in FPS rate
         is very small (<1FPS or so). Not a big issue, but that is causing
         some CTS tests to fail.
      
      In addition to that VRR technology (or seamless mode switching) require
      hwcomposer to group modes which tells the framework that seamless mode
      configuration change is supported within a group of display modes.
      
      By this commit do the following:
      1. Group modes by the resolution:
         E.g.
      
          Group 1:
          1024x768i@60
          1024x768i@90
          1024x768@50
          1024x768@50.1
      
          Group 2:
          1920x1080@60
          1920x1080@24.3
          1920x1080i@60
          1920x1080i@120
      
      2. Disable modes in a way that each group keeps only interlaced or proressive
         modes enabled. In case KMS reported preferred mode is interlaced - prefer
         interlaced for the whole group, otherwise prefer progressive.
      
      3. Disable mode in case different mode in the same group has similar frequency
         with delta less than 1FPS.
      
      4. Report only modes which remain enabled to the framework.
      
      Test: atest CtsGraphicsTestCases
      
      Signed-off-by: default avatarRoman Stratiienko <roman.o.stratiienko@globallogic.com>
      a148f213
  9. 10 Nov, 2021 2 commits
  10. 28 Oct, 2021 2 commits
  11. 23 Oct, 2021 9 commits
  12. 22 Oct, 2021 1 commit
  13. 29 Sep, 2021 12 commits