From: Abhinav Parihar <abhinav.parihar@oss.qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
srinivas.kandagatla@linaro.org, linux-arm-msm@vger.kernel.org
Cc: 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: Re: [PATCH v1] arm64: dts: qcom: Remove FastRPC compute CB9 entries
Date: Thu, 22 Oct 2026 14:57:38 +0530 [thread overview]
Message-ID: <28a4a452-340c-4ac6-afba-5cd39b370ceb@oss.qualcomm.com> (raw)
In-Reply-To: <b0763841-cfe9-4355-b900-ae43d93dedf6@oss.qualcomm.com>
On 10/16/2026 2:15 PM, Konrad Dybcio wrote:
> On 10/16/26 7:20 AM, Abhinav Parihar wrote:
>> Context bank 9 is reserved for secure use cases and must not be exposed
>> as a FastRPC compute context bank for non-secure offloading.
> The lack of a platform name in the commit message and a split over that
> suggests this is a universal truth for all Qualcomm platforms, yet the
> patch only limits this to some of those who currently define a cb@9.
>
> Please make it more clear which one is intended.
Ack, patch v2 will have patch series including removal from all
platforms having cb@9
>> Remove the compute-cb@9 nodes from the Lemans and Monaco device trees to
>> prevent clients from selecting a secure context bank for normal FastRPC
>> workloads.
>>
>> Secure use case support is not currently implemented upstream.
> Ordering this sentence before the previous paragraph would make the
> commit message read more naturally
>
> Konrad
Ack
next prev parent reply other threads:[~2026-10-22 9:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 5:20 Abhinav Parihar
2026-10-16 8:45 ` Konrad Dybcio
2026-10-22 9:27 ` Abhinav Parihar [this message]
2026-10-16 10:03 ` Ekansh Gupta
2026-10-22 9:06 ` Abhinav Parihar
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=28a4a452-340c-4ac6-afba-5cd39b370ceb@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=konrad.dybcio@oss.qualcomm.com \
--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®