From: Bjorn Andersson <andersson@kernel.org>
To: Vishnu Santhosh <vishnu.santhosh@oss.qualcomm.com>
Cc: Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, chris.lew@oss.qualcomm.com,
Deepak Kumar Singh <deepak.singh@oss.qualcomm.com>
Subject: Re: [PATCH] arm64: dts: qcom: shikra: Add qcom,vmid to BAM-DMA node
Date: Tue, 4 Aug 2026 22:38:24 -0500 [thread overview]
Message-ID: <anKwCKnt-3wrtzRt@baldur> (raw)
In-Reply-To: <a8862b6a-28fb-492b-83c9-a02730fc366b@oss.qualcomm.com>
On Tue, Aug 04, 2026 at 09:49:18PM +0530, Vishnu Santhosh wrote:
>
> On 31-07-2026 02:49 am, Bjorn Andersson wrote:
> > On Tue, Jul 14, 2026 at 02:01:53PM +0530, Vishnu Santhosh wrote:
> > > On the Qualcomm Shikra SoC the mDSP (VMID 43 / QCOM_SCM_VMID_NAV) is
> > > the AXI master for BAM descriptor FIFO accesses. The XPU enforces
> > > per-region access control; without an SCM assignment granting NAV
> > > access, the first DMA transfer triggers an XPU violation.
> > >
> > I'm a bit puzzled about your plan here.
> >
> > You posted this on July 14th, that's 3 days after I asked you to rebase
> > patch [1]. This patch literally says that [1] is broken and untested.
>
> The XPU violation itself wasn't visible against the base bam-dmux
> enablement alone. It only showed up once the access-control policy was
> enabled, which happened to land close to when [1] was posted upstream.
> That's why this series followed so soon after.
>
Are you saying that none of the shikra patches were tested with
access-control enabled?!
Regards,
Bjorn
next prev parent reply other threads:[~2026-08-05 3:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 8:31 [PATCH] arm64: dts: qcom: shikra: Add qcom,vmid to BAM-DMA node Vishnu Santhosh
2026-07-30 21:19 ` Bjorn Andersson
2026-08-04 16:19 ` Vishnu Santhosh
2026-08-05 3:38 ` Bjorn Andersson [this message]
2026-08-05 8:20 ` Vishnu Santhosh
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=anKwCKnt-3wrtzRt@baldur \
--to=andersson@kernel.org \
--cc=chris.lew@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=deepak.singh@oss.qualcomm.com \
--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=robh@kernel.org \
--cc=vishnu.santhosh@oss.qualcomm.com \
/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