From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] arm64: dts: qcom: lemans: disable zap-shader for EL2 configuration
Date: Wed, 28 Jan 2026 13:18:38 +0100 [thread overview]
Message-ID: <4a59fb83-6682-41c8-a420-6fbc472ee63c@oss.qualcomm.com> (raw)
In-Reply-To: <20260127-talos-el2-overlay-v2-1-b6a2266532c4@oss.qualcomm.com>
On 1/27/26 12:43 PM, Mukesh Ojha wrote:
> 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.
>
> Signed-off-by: Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>
> ---
Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Konrad
next prev parent reply other threads:[~2026-01-28 12:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 11:43 [PATCH v2 0/3] arm64: dts: qcom: Add EL2 overlay support Mukesh Ojha
2026-01-27 11:43 ` [PATCH v2 1/3] arm64: dts: qcom: lemans: disable zap-shader for EL2 configuration Mukesh Ojha
2026-01-28 12:18 ` Konrad Dybcio [this message]
2026-01-27 11:43 ` [PATCH v2 2/3] arm64: dts: qcom: monaco: Add EL2 overlay Mukesh Ojha
2026-01-28 12:19 ` Konrad Dybcio
2026-01-27 11:43 ` [PATCH v2 3/3] arm64: dts: qcom: talos: " Mukesh Ojha
2026-03-10 2:45 ` [PATCH v2 0/3] arm64: dts: qcom: Add EL2 overlay support Bjorn Andersson
2026-03-24 6:46 ` Mukesh Ojha
2026-04-05 19:40 ` (subset) " Bjorn Andersson
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=4a59fb83-6682-41c8-a420-6fbc472ee63c@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mukesh.ojha@oss.qualcomm.com \
--cc=robh@kernel.org \
/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