From: Ekansh Gupta <ekansh.gupta@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: konrad.dybcio@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>,
quic_bkumar@quicinc.com, quic_chennak@quicinc.com,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] arm64: dts: qcom: talos: Add memory-region for audio PD
Date: Mon, 27 Apr 2026 16:31:04 +0530 [thread overview]
Message-ID: <48ecf277-da46-4994-87c7-7eef66956cda@oss.qualcomm.com> (raw)
In-Reply-To: <jjnciedre42mqllwoe4mkmi7a355itmbcmuhc3oyrpdjyitnkj@mntkm4zonfdq>
On 25-04-2026 20:43, Dmitry Baryshkov wrote:
> On Fri, Apr 24, 2026 at 03:40:22PM +0530, Ekansh Gupta via B4 Relay wrote:
>> From: Ekansh Gupta <ekansh.gupta@oss.qualcomm.com>
>>
>> Reserve memory region for audio PD dynamic loading and remote heap
>> requirements. Add the required VMID list for memory ownership
>> transfers.
>
> And what happens if there is no such region allocated / assigned?
If there is no region assigned and audio PD dynamic loading is requested
for any offload use-case, it would result in audio PD dynamic loading
failure which is the major purpose of audio fastrpc daemon.
>
> Also, can we please get the remote heap set up for all the platforms
> where it makes sense? I see that it is only currently set for a very few
> devices (hamoa, kodiak, lemans, monaco and SM8750). Checking the
> downstream sources, I see the remoteheap being set starting from the
> era of MSM8996 / SDM660.
Noted. I'll bring this region for other platforms also.
>
>> Signed-off-by: Ekansh Gupta <ekansh.gupta@oss.qualcomm.com>
>
next prev parent reply other threads:[~2026-04-27 11:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-24 10:10 [PATCH v3] arm64: dts: qcom: talos: Add memory-region for audio PD Ekansh Gupta via B4 Relay
2026-04-25 15:13 ` Dmitry Baryshkov
2026-04-27 11:01 ` Ekansh Gupta [this message]
2026-04-27 12:52 ` 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=48ecf277-da46-4994-87c7-7eef66956cda@oss.qualcomm.com \
--to=ekansh.gupta@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konrad.dybcio@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=quic_bkumar@quicinc.com \
--cc=quic_chennak@quicinc.com \
--cc=robh@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