From: Abhinav Parihar <abhinav.parihar@oss.qualcomm.com>
To: srinivas.kandagatla@linaro.org, linux-arm-msm@vger.kernel.org
Cc: Abhinav Parihar <abhinav.parihar@oss.qualcomm.com>,
gregkh@linuxfoundation.org, quic_bkumar@quicinc.com,
ekansh.gupta@oss.qualcomm.com, linux-kernel@vger.kernel.org,
quic_chennak@quicinc.com, dri-devel@lists.freedesktop.org,
arnd@arndb.de
Subject: [PATCH v2 0/6] arm64: dts: qcom: Remove FastRPC compute CB9 entries
Date: Fri, 23 Oct 2026 14:33:02 +0530 [thread overview]
Message-ID: <20261023090308.2898683-1-abhinav.parihar@oss.qualcomm.com> (raw)
Context bank 9 (CB9) is reserved for secure use cases and must not be
exposed as a FastRPC compute context bank for non-secure offloading.
Several Qualcomm platform device trees currently define compute-cb@9
nodes, which allows non-secure clients to select a context bank that is
intended for secure use. Remove these CB9 entries from all affected
platforms to prevent unintended usage and align the device trees with
the intended security model.
This series removes the compute-cb@9 nodes from all affected Qualcomm
platform DTSI files.
Patch [v1]: https://lore.kernel.org/all/20261016052042.3755352-1-abhinav.parihar@oss.qualcomm.com/
Changes in v2:
- Split the changes from a single patch into a per-platform patch series.
- No functional changes.
Abhinav Parihar (6):
arm64: dts: qcom: lemans: Remove FastRPC compute CB9 entry
arm64: dts: qcom: monaco: Remove FastRPC compute CB9 entry
arm64: dts: qcom: sc8280xp: Remove FastRPC compute CB9 entry
arm64: dts: qcom: sdm660: Remove FastRPC compute CB9 entry
arm64: dts: qcom: sdm630: Remove FastRPC compute CB9 entry
arm64: dts: qcom: msm8996: Remove FastRPC compute CB9 entry
arch/arm64/boot/dts/qcom/lemans.dtsi | 16 ----------------
arch/arm64/boot/dts/qcom/monaco.dtsi | 7 -------
arch/arm64/boot/dts/qcom/msm8996.dtsi | 6 ------
arch/arm64/boot/dts/qcom/sc8280xp.dtsi | 6 ------
arch/arm64/boot/dts/qcom/sdm630.dtsi | 5 -----
arch/arm64/boot/dts/qcom/sdm660.dtsi | 6 ------
6 files changed, 46 deletions(-)
--
2.34.1
next reply other threads:[~2026-10-23 9:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 9:03 Abhinav Parihar [this message]
2026-10-23 9:03 ` [PATCH v2 1/6] arm64: dts: qcom: lemans: Remove FastRPC compute CB9 entry Abhinav Parihar
2026-10-26 5:31 ` Ekansh Gupta
2026-10-26 12:01 ` Konrad Dybcio
2026-10-23 9:03 ` [PATCH v2 2/6] arm64: dts: qcom: monaco: " Abhinav Parihar
2026-10-26 5:31 ` Ekansh Gupta
2026-10-26 12:01 ` Konrad Dybcio
2026-10-23 9:03 ` [PATCH v2 3/6] arm64: dts: qcom: sc8280xp: " Abhinav Parihar
2026-10-26 5:31 ` Ekansh Gupta
2026-10-26 11:59 ` Konrad Dybcio
2026-10-26 11:59 ` Konrad Dybcio
2026-10-23 9:03 ` [PATCH v2 4/6] arm64: dts: qcom: sdm660: " Abhinav Parihar
2026-10-26 5:31 ` Ekansh Gupta
2026-10-26 12:15 ` Konrad Dybcio
2026-10-23 9:03 ` [PATCH v2 5/6] arm64: dts: qcom: sdm630: " Abhinav Parihar
2026-10-26 5:32 ` Ekansh Gupta
2026-10-26 12:16 ` Konrad Dybcio
2026-10-23 9:03 ` [PATCH v2 6/6] arm64: dts: qcom: msm8996: " Abhinav Parihar
2026-10-26 5:32 ` Ekansh Gupta
2026-10-26 12:08 ` Konrad Dybcio
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=20261023090308.2898683-1-abhinav.parihar@oss.qualcomm.com \
--to=abhinav.parihar@oss.qualcomm.com \
--cc=arnd@arndb.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=ekansh.gupta@oss.qualcomm.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_bkumar@quicinc.com \
--cc=quic_chennak@quicinc.com \
--cc=srinivas.kandagatla@linaro.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
all inboxes | Powered by JetHome®