From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Iranna Mundaganur <iranna.mundaganur@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>,
Sibi Sankar <sibi.sankar@oss.qualcomm.com>,
Abel Vesa <abel.vesa@oss.qualcomm.com>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Sairamreddy Bojja <sairamreddy.bojja@oss.qualcomm.com>
Subject: Re: [PATCH] arm64: dts: qcom: glymur: Fix missing SMMU stream IDs for ADSP
Date: Mon, 24 Aug 2026 08:51:54 +0200 [thread overview]
Message-ID: <e783bccf-4f0d-453c-961d-0bc8999c4bc2@oss.qualcomm.com> (raw)
In-Reply-To: <0ebdf8fd-de3f-418c-95d4-17474075bd55@oss.qualcomm.com>
On 8/21/26 8:59 AM, Iranna Mundaganur wrote:
>
> On 19-08-2026 17:16, Konrad Dybcio wrote:
>> On 8/11/26 6:44 PM, Iranna Mundaganur wrote:
>>> From: Sairamreddy Bojja <sairamreddy.bojja@oss.qualcomm.com>
>>>
>>> Add the missing SIDs for the LPASS eNPU masters to the ADSP
>>> iommus list. These masters are exercised during audio record
>>> use cases where Environmental Acoustic Intelligence (EAI)
>>> models run on the eNPUs.
>> Could you share a bit more details on how we can reproduce t his?
>
> This use case is not enabled upstream yet, we validate it downstream with the
> AudioReach application where EAI models run on eNPU0/eNPU1 and need memory
> access from those masters.
I figured it may need additional changes. It would still be really
useful to know how to reproduce that, even if it's a little involved.
Konrad
prev parent reply other threads:[~2026-08-24 6:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 16:44 Iranna Mundaganur
2026-08-11 19:41 ` Abel Vesa
2026-08-19 11:46 ` Konrad Dybcio
2026-08-21 7:24 ` Iranna Mundaganur
2026-08-31 16:25 ` Bjorn Andersson
2026-09-03 4:17 ` Iranna Mundaganur
[not found] ` <0ebdf8fd-de3f-418c-95d4-17474075bd55@oss.qualcomm.com>
2026-08-24 6:51 ` Konrad Dybcio [this message]
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=e783bccf-4f0d-453c-961d-0bc8999c4bc2@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=abel.vesa@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=iranna.mundaganur@oss.qualcomm.com \
--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=sairamreddy.bojja@oss.qualcomm.com \
--cc=sibi.sankar@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
all inboxes | Powered by JetHome®