From: Komal Bajaj <komal.bajaj@oss.qualcomm.com>
To: sashiko-reviews@lists.linux.dev
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 2/2] arm64: dts: qcom: shikra: Add EL2 overlay for remoteproc SMMU mappings
Date: Thu, 1 Oct 2026 11:50:46 +0530 [thread overview]
Message-ID: <6a685e0b-c198-49ff-8941-5017fdbd48c2@oss.qualcomm.com> (raw)
In-Reply-To: <20260930115553.C3CA71F000FF@smtp.kernel.org>
On 9/30/2026 5:25 PM, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
> - [Medium] Missing EL2 targets for camera EVK variants
> - [Medium] Undocumented disablement of GPU zap shader in EL2 overlay
> --
>
> commit 07c9abdfac5fabfba8cfb72f094624db1d5cb41b
> Author: Komal Bajaj <komal.bajaj@oss.qualcomm.com>
>
> arm64: dts: qcom: shikra: Add EL2 overlay for remoteproc SMMU mappings
>
> This commit introduces an EL2-specific DeviceTree overlay for Shikra boards.
> It explicitly configures the firmware IOMMU streams for remote processors,
> allowing Linux to boot directly at EL2 without a hypervisor.
>
>> diff --git a/arch/arm64/boot/dts/qcom/Makefile b/arch/arm64/boot/dts/qcom/Makefile
>> index 4e714251d5e6b..634914b8f229b 100644
>> --- a/arch/arm64/boot/dts/qcom/Makefile
>> +++ b/arch/arm64/boot/dts/qcom/Makefile
> [ ... ]
>> @@ -377,6 +388,7 @@ shikra-iqs-evk-imx577-camera-dtbs := shikra-iqs-evk.dtb shikra-iqs-evk-imx577-ca
>> dtb-$(CONFIG_ARCH_QCOM) += shikra-cqm-evk-imx577-camera.dtb
>> dtb-$(CONFIG_ARCH_QCOM) += shikra-cqs-evk-imx577-camera.dtb
>> dtb-$(CONFIG_ARCH_QCOM) += shikra-iqs-evk-imx577-camera.dtb
> [Severity: Medium]
> The commit message states the overlay is applied to "all Shikra EVK variants
> devices", but are we missing the EL2 targets for these camera variants?
>
> Without adding targets like shikra-cqm-evk-imx577-camera-el2-dtbs, the camera
> variants cannot be built or booted natively at EL2.
Camera variants have not yet been validated in EL2, so the corresponding
*-el2-dtbs targets were not added.
We will add them in a follow-up change once EL2 validation is completed.
>> +
>> dtb-$(CONFIG_ARCH_QCOM) += sm4250-oneplus-billie2.dtb
> [ ... ]
>
>> diff --git a/arch/arm64/boot/dts/qcom/shikra-el2.dtso b/arch/arm64/boot/dts/qcom/shikra-el2.dtso
>> new file mode 100644
>> index 0000000000000..d2f3186bd47db
>> --- /dev/null
>> +++ b/arch/arm64/boot/dts/qcom/shikra-el2.dtso
>> @@ -0,0 +1,23 @@
>> +// SPDX-License-Identifier: BSD-3-Clause
>> +/*
>> + * Copyright (c) Qualcomm Technologies, Inc. and/or its subsidiaries.
>> + *
>> + * Shikra specific modifications required to boot in EL2.
>> + */
>> +
>> +/dts-v1/;
>> +/plugin/;
>> +
>> +&gpu_zap_shader {
>> + status = "disabled";
>> +};
> [Severity: Medium]
> Is it intended to disable the GPU zap shader in this overlay without
> mentioning it in the commit message?
>
> The commit message only describes adding remoteproc SMMU mappings. While
> disabling the zap shader might be necessary for EL2 boot, this hardware
> feature disablement is currently an undocumented side effect.
Zap shader is not required in EL2, as Linux can perform GPU zap sequence
on its own. Disabling it is intentional.
Thanks
Komal
prev parent reply other threads:[~2026-10-01 6:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 11:49 [PATCH v2 0/2] arm64: dts: qcom: shikra: Add EL2 overlay for EVK variants Komal Bajaj
2026-09-30 11:49 ` [PATCH v2 1/2] dt-bindings: remoteproc: qcom: Relax PAS iommus item limit Komal Bajaj
2026-10-01 8:33 ` Krzysztof Kozlowski
2026-10-05 9:50 ` Komal Bajaj
2026-09-30 11:49 ` [PATCH v2 2/2] arm64: dts: qcom: shikra: Add EL2 overlay for remoteproc SMMU mappings Komal Bajaj
2026-09-30 11:55 ` sashiko-bot
2026-10-01 6:20 ` Komal Bajaj [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6a685e0b-c198-49ff-8941-5017fdbd48c2@oss.qualcomm.com \
--to=komal.bajaj@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox