Skip to content

Add eDP display overlays for hamoa and purwa IoT EVKs - #977

Open
anan-tiwa wants to merge 2 commits into
qualcomm-linux:qcom-6.18.yfrom
anan-tiwa:edp_overlay_hamoa_purwa_qli_2_0
Open

Add eDP display overlays for hamoa and purwa IoT EVKs#977
anan-tiwa wants to merge 2 commits into
qualcomm-linux:qcom-6.18.yfrom
anan-tiwa:edp_overlay_hamoa_purwa_qli_2_0

Conversation

@anan-tiwa

Copy link
Copy Markdown

Both Hamoa and Purwa IoT EVKs are available in headed and headless
variants. The headed variants use an eDP display panel connected via
the DP3 controller, while the headless variants do not include a
display.

The existing DT is causing the eDP-panel driver to probe an unavailable
panel, resulting in AUX probe timeouts and missing display modes.
Userspace then attempts display commits through the eDP connector,
causing repeated DPU vblank, frame-done, and IRQ timeout errors.

Move the eDP-specific nodes out of the base DTS files into separate
DTBO overlays for each board. This allows the base DTBs to be used
as-is for headless variants, while the composite DTBs enable eDP
support on headed variants.

CRs-Fixed: 4543794, 4543797

@qswat-orbit-external

Copy link
Copy Markdown

Merge Check Failed: No Change Task Found

No associated change tasks found for CR 4543794 on any of the following entities:

Entities:

  • kernel.qli.2.0

CR: 4543794

Please ensure the CR has a change task associated with at least one of the entities for this branch.

Anand Tiwari added 2 commits August 19, 2026 08:56
Hamoa IoT EVKs are available with and without an eDP panel. When the
panel is absent, DP3 is unused, but the base DTS still describes the
eDP panel and display path.

This causes the eDP driver to probe an unavailable panel, resulting in
AUX probe timeouts and missing display modes. Userspace then attempts
display commits through the eDP connector, causing repeated DPU vblank,
frame-done, and IRQ timeout errors.

Move the eDP-specific nodes into an overlay so the base DTB describes
the configuration without the panel, while the overlay enables eDP for
boards with the panel connected.

DT overlays cannot remove properties from a node defined in the base
DTB, so the /delete-property/ of #sound-dai-cells is moved into the
base DTS instead of the overlay, where it takes effect.

Link: https://lore.kernel.org/all/20260818-edp_overlay_for-next-v2-1-bd811d378fb7@oss.qualcomm.com/

Signed-off-by: Anand Tiwari <anand.tiwari@oss.qualcomm.com>
Purwa IoT EVKs are available with and without an eDP panel. When the
panel is absent, DP3 is unused, but the base DTS still describes the
eDP panel and display path.

This causes the eDP driver to probe an unavailable panel, resulting in
AUX probe timeouts and missing display modes. Userspace then attempts
display commits through the eDP connector, causing repeated DPU vblank,
frame-done, and IRQ timeout errors.

Move the eDP-specific nodes into an overlay so the base DTB describes
the configuration without the panel, while the overlay enables eDP for
boards with the panel connected.

DT overlays cannot remove properties from a node defined in the base
DTB, so the /delete-property/ of #sound-dai-cells is moved into the
base DTS instead of the overlay, where it takes effect.

Link: https://lore.kernel.org/all/20260818-edp_overlay_for-next-v2-2-bd811d378fb7@oss.qualcomm.com/

Signed-off-by: Anand Tiwari <anand.tiwari@oss.qualcomm.com>
@anan-tiwa
anan-tiwa force-pushed the edp_overlay_hamoa_purwa_qli_2_0 branch from 6b04836 to c89e167 Compare August 19, 2026 03:33
@qswat-orbit-external

Copy link
Copy Markdown

Merge Check Failed: CR Not Eligible for Merge

CR 4543794 is not eligible for merge.

The parent software image for kernel.qli.2.0 is not development complete.

Entity: kernel.qli.2.0
CR: 4543794
Reason: CR_CANNOT_MERGE

Please ensure the CR passes both CCT (ComponentChangeTasks) and ICT (Integration Change Tasks) validations.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant