From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Karthik S <karthik.s@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>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/2] arm64: dts: qcom: qcs6490-rb3gen2: add audio CMA memory region for AudioReach
Date: Tue, 25 Aug 2026 15:48:32 +0200 [thread overview]
Message-ID: <eedc1702-7767-4d5c-8077-20432766c613@oss.qualcomm.com> (raw)
In-Reply-To: <20260825133333.376591-2-karthik.s@oss.qualcomm.com>
On 8/25/26 3:33 PM, Karthik S wrote:
> Add a dynamic CMA pool for the AudioReach audio stack on qcs6490-rb3gen2.
> Use alloc-ranges to let the kernel pick a free address rather than a fixed
> reg, which avoided EFI-reserved memory at 0x9cc00000. Add 4 MiB alignment
> to satisfy CMA_MIN_ALIGNMENT_BYTES. Wire memory-region into q6apmdai so
> the q6apm-audio-mem-cma child driver can attach the pool.
>
> Based on the equivalent implementation for lemans (SA8295P).
>
> Signed-off-by: Karthik S <karthik.s@oss.qualcomm.com>
> ---
Please don't send patches that you haven't compile-tested
Konrad
next prev parent reply other threads:[~2026-08-25 13:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 13:33 [PATCH v1 0/2] CMA-memory-to-offload-FNN-PLUS-module-to-eNPU Karthik S
2026-08-25 13:33 ` [PATCH v1 1/2] arm64: dts: qcom: qcs6490-rb3gen2: add audio CMA memory region for AudioReach Karthik S
2026-08-25 13:34 ` Krzysztof Kozlowski
2026-08-25 13:42 ` Krzysztof Kozlowski
2026-08-25 13:48 ` Konrad Dybcio [this message]
2026-08-25 13:33 ` [PATCH v1 2/2] arm64: dts: qcom: kodiak-el2: add LPASS AML IOMMU SIDs for eNPU audio offload Karthik S
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=eedc1702-7767-4d5c-8077-20432766c613@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=karthik.s@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 \
/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