Skip to content
Snippets Groups Projects
  1. Mar 03, 2025
  2. Feb 19, 2025
  3. Feb 18, 2025
  4. Feb 17, 2025
  5. Feb 14, 2025
  6. Feb 07, 2025
  7. Feb 06, 2025
  8. Feb 04, 2025
  9. Feb 03, 2025
  10. Jan 31, 2025
    • Tobias Kahlki's avatar
    • Dietmar Muscholik's avatar
      [E81] Add enable-gpio and backlight to eDP-displays · 2d310366
      Dietmar Muscholik authored and Tobias Kahlki's avatar Tobias Kahlki committed
      In the DP-driver there is "qcom,edp-vcc-en-gpio" that a gpio can be
      assigned to in the DT and that powers on the display. But this gpio is
      switched AFTER the display has been powered on. Thus there is no other
      way to turn on a display but using a hog-gpio.
      
      There is no way to assign a backlight-device to (e)DP, not even a PWM,
      only a bunch of gpios. So the pwm is configured as gpio, meaning there is
      no way to adjust the backlight-brightness but 2 ways to switch the
      backlight off, because both gpios must be high.
      2d310366
    • Dietmar Muscholik's avatar
      [E81] Add symbolic name for LCD0_VDD_EN_PIN to e81-pinfunc.h · 04525c45
      Dietmar Muscholik authored and Tobias Kahlki's avatar Tobias Kahlki committed
      This is used to enable an eDP with a hog-gpio
      04525c45
    • Tobias Kahlki's avatar
      [E81] Add dtsi-files for QCS5430-FP1 and QCS6490 · c659e265
      Tobias Kahlki authored
      The QCS5430 is a QCS6490 that is lacking some features, so we use the
      QCS6490 dtsi-file for both and disable the non-existing features for
      QCS5430. The opposite way would be less ugly but would require modification
      of the Qualcomm-provided dtsi-files.
      c659e265
    • Dietmar Muscholik's avatar
      [E81] Add dtsi-files for eDP · 12d64ce9
      Dietmar Muscholik authored and Tobias Kahlki's avatar Tobias Kahlki committed
      Qualcomm uses off-tree device-tree-overlays for displays. These overlays are
      applied to the base device-tree at build time to generate a combined device-
      tree.
      Because they are maintained in separate repositories they do not necessarily
      match the kernel. If so, for the dtc everything seems to be right, because it
      has no knowledge about the base device-tree. The errors, like the most common
      "unknown label" because of a simple typo, occure later when the overlays are
      applied. While the dtc says: this file, this line, this error, the tool that
      applies the overlays only says "FDT_ERR_NOTFOUND", hidden somewhere in the
      bitbake-logs, and it takes hours and hours of trial-and-error to figure out
      what went wrong.
      Furthermore, because the overlays are not applied dynamically at runtime but
      at build-time, it does not make any sense to use overlays. They cause nothing
      but trouble. For this reasons th overlays have been turned to dtsi-files.
      12d64ce9
  11. Jan 30, 2025
  12. Jan 27, 2025
  13. Jan 17, 2025
Loading