Skip to content

Add El2 overlay and disable zap-shader for EL2 configuration#230

Closed
shivrawa wants to merge 3 commits intoqualcomm-linux:qcom-6.18.yfrom
shivrawa:qcom-6.18.y
Closed

Add El2 overlay and disable zap-shader for EL2 configuration#230
shivrawa wants to merge 3 commits intoqualcomm-linux:qcom-6.18.yfrom
shivrawa:qcom-6.18.y

Conversation

@shivrawa
Copy link

@shivrawa shivrawa commented Feb 4, 2026

We don't need to use zap shader in EL2 as Linux can zap the gpu on it's own. Lets disable zap-shader for Lemans EL2 configuration.

Add a EL2-specific DT overlay and apply it to Monaco IOT variant devices to create -el2.dtb for each of them alongside "normal" dtb.

Add a EL2-specific DT overlay and apply it to Talos IOT variant devices to create -el2.dtb for each of them alongside "normal" dtb.

CRs-Fixed: 4353993

…uration

We don't need to use zap shader in EL2 as Linux can zap the gpu on
it's own. Lets disable zap-shader for Lemans EL2 configuration.

Link: https://lore.kernel.org/lkml/20260127-talos-el2-overlay-v2-1-b6a2266532c4@oss.qualcomm.com/
Signed-off-by: Shivam Rawat <shivrawa@qti.qualcomm.com>
All the Monaco IOT variants boards are using Gunyah hypervisor which
means that, so far, Linux-based OS could only boot in EL1 on those
devices.  However, it is possible for us to boot Linux at EL2 on these
devices [1].

When running under Gunyah, the remote processor firmware IOMMU streams
are controlled by Gunyah. However, without Gunyah, the IOMMU is managed
by the consumer of this DeviceTree. Therefore, describe the firmware
streams for each remote processor.

Add a EL2-specific DT overlay and apply it to Monaco IOT variant
devices to create -el2.dtb for each of them alongside "normal" dtb.

[1]
https://docs.qualcomm.com/bundle/publicresource/topics/80-70020-4/boot-developer-touchpoints.html#uefi

Link: https://lore.kernel.org/lkml/20260127-talos-el2-overlay-v2-2-b6a2266532c4@oss.qualcomm.com/
Signed-off-by: Shivam Rawat <shivrawa@qti.qualcomm.com>
All the existing variants Talos boards are using Gunyah hypervisor
which means that, so far, Linux-based OS could only boot in EL1 on
those devices.  However, it is possible for us to boot Linux at EL2
on these devices [1].

When running under Gunyah, the remote processor firmware IOMMU streams
are controlled by Gunyah. However, without Gunyah, the IOMMU is managed
by the consumer of this DeviceTree. Therefore, describe the firmware
streams for each remote processor.

Add a EL2-specific DT overlay and apply it to Talos IOT variant
devices to create -el2.dtb for each of them alongside "normal" dtb.
[1]
https://docs.qualcomm.com/bundle/publicresource/topics/80-70020-4/boot-developer-touchpoints.html#uefi

Link: https://lore.kernel.org/lkml/20260127-talos-el2-overlay-v2-3-b6a2266532c4@oss.qualcomm.com/
Signed-off-by: Shivam Rawat <shivrawa@qti.qualcomm.com>
@shivrawa shivrawa changed the title FROMLIST: arm64: dts: qcom: lemans: disable zap-shader for EL2 configuration Add El2 overlay and disable zap-shader for EL2 configuration Feb 4, 2026
@shivrawa
Copy link
Author

shivrawa commented Feb 4, 2026

PR already present : #203

@shivrawa shivrawa closed this Feb 4, 2026
@shivrawa
Copy link
Author

shivrawa commented Feb 4, 2026

PR already present : #203

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