mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Abhinav Parihar <abhinav.parihar@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, stable@vger.kernel.org
Subject: Re: [PATCH v2 5/6] arm64: dts: qcom: sdm630: Remove FastRPC compute CB9 entry
Date: Mon, 26 Oct 2026 13:16:03 +0100	[thread overview]
Message-ID: <673273c0-efd3-4ee7-a008-7e70fdada1b9@oss.qualcomm.com> (raw)
In-Reply-To: <20261023090308.2898683-6-abhinav.parihar@oss.qualcomm.com>

On 10/23/26 11:03 AM, Abhinav Parihar wrote:
> Remove the compute-cb@9 nodes from sdm630 device tree to
> prevent clients from selecting a secure context bank for normal FastRPC
> workloads.
> 
> Secure use case support is not currently implemented upstream.
> 
> Fixes: e8e1fb5c703f ("arm64: dts: qcom: sdm630: set adsp compute-cbs' regs properly")
> Cc: stable@vger.kernel.org
> Signed-off-by: Abhinav Parihar <abhinav.parihar@oss.qualcomm.com>
> ---
>  arch/arm64/boot/dts/qcom/sdm630.dtsi | 5 -----
>  1 file changed, 5 deletions(-)
> 
> diff --git a/arch/arm64/boot/dts/qcom/sdm630.dtsi b/arch/arm64/boot/dts/qcom/sdm630.dtsi
> index a41ba0da380b..721885455639 100644
> --- a/arch/arm64/boot/dts/qcom/sdm630.dtsi
> +++ b/arch/arm64/boot/dts/qcom/sdm630.dtsi
> @@ -2483,11 +2483,6 @@ compute-cb@8 {
>  						iommus = <&lpass_smmu 8>;
>  					};
>  
> -					compute-cb@9 {
> -						compatible = "qcom,fastrpc-compute-cb";
> -						reg = <9>;
> -						iommus = <&lpass_smmu 9>;
> -					};

I think 4/5 are secure on LPASS on 630.

Konrad

  parent reply	other threads:[~2026-10-26 12:16 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-23  9:03 [PATCH v2 0/6] arm64: dts: qcom: Remove FastRPC compute CB9 entries Abhinav Parihar
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 [this message]
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=673273c0-efd3-4ee7-a008-7e70fdada1b9@oss.qualcomm.com \
    --to=konrad.dybcio@oss.qualcomm.com \
    --cc=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 \
    --cc=stable@vger.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

all inboxes | Powered by JetHome®