From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: Raj Kumar Bhagat <quic_rajkbhag@quicinc.com>,
Johannes Berg <johannes@sipsolutions.net>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jeff Johnson <jjohnson@kernel.org>
Cc: linux-wireless@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, ath12k@lists.infradead.org,
Vasanthakumar Thiagarajan
<vasanthakumar.thiagarajan@oss.qualcomm.com>
Subject: Re: [PATCH ath-next v12 07/13] wifi: ath12k: add support for fixed QMI firmware memory
Date: Fri, 21 Mar 2025 09:02:26 -0700 [thread overview]
Message-ID: <72e9ddb1-c0eb-4eea-aa11-3f24ed0caea2@oss.qualcomm.com> (raw)
In-Reply-To: <20250321-ath12k-ahb-v12-7-bb389ed76ae5@quicinc.com>
On 3/21/2025 3:52 AM, Raj Kumar Bhagat wrote:
> IPQ5332 firmware supports only fixed QMI firmware memory.
>
> Hence, add support to read reserved fixed memory region from
> device-tree and provide the reserved memory segments for
> firmware to use during QMI firmware memory request.
Be aware that new memory-region helpers are being introduced by Rob:
https://msgid.link/20250317232426.952188-1-robh@kernel.org
/jeff
next prev parent reply other threads:[~2025-03-21 16:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 10:52 [PATCH ath-next v12 00/13] wifi: ath12k: add Ath12k AHB driver support for IPQ5332 Raj Kumar Bhagat
2025-03-21 10:52 ` [PATCH ath-next v12 01/13] dt-bindings: net: wireless: describe the ath12k AHB module " Raj Kumar Bhagat
2025-03-21 10:52 ` [PATCH ath-next v12 02/13] wifi: ath12k: fix incorrect CE addresses Raj Kumar Bhagat
2025-03-21 10:52 ` [PATCH ath-next v12 03/13] wifi: ath12k: refactor ath12k_hw_regs structure Raj Kumar Bhagat
2025-03-21 10:52 ` [PATCH ath-next v12 04/13] wifi: ath12k: add ath12k_hw_params for IPQ5332 Raj Kumar Bhagat
2025-03-21 10:52 ` [PATCH ath-next v12 05/13] wifi: ath12k: avoid m3 firmware download in AHB device IPQ5332 Raj Kumar Bhagat
2025-03-21 10:52 ` [PATCH ath-next v12 06/13] wifi: ath12k: Add hw_params to remap CE register space for IPQ5332 Raj Kumar Bhagat
2025-03-21 10:52 ` [PATCH ath-next v12 07/13] wifi: ath12k: add support for fixed QMI firmware memory Raj Kumar Bhagat
2025-03-21 16:02 ` Jeff Johnson [this message]
2025-03-21 10:52 ` [PATCH ath-next v12 08/13] wifi: ath12k: add AHB driver support for IPQ5332 Raj Kumar Bhagat
2025-03-25 2:34 ` Vasanthakumar Thiagarajan
2025-03-21 10:52 ` [PATCH ath-next v12 09/13] wifi: ath12k: Power up root PD Raj Kumar Bhagat
2025-03-21 10:52 ` [PATCH ath-next v12 10/13] wifi: ath12k: Register various userPD interrupts and save SMEM entries Raj Kumar Bhagat
2025-03-21 10:52 ` [PATCH ath-next v12 11/13] wifi: ath12k: Power up userPD Raj Kumar Bhagat
2025-03-21 10:52 ` [PATCH ath-next v12 12/13] wifi: ath12k: Power down userPD Raj Kumar Bhagat
2025-03-21 10:52 ` [PATCH ath-next v12 13/13] wifi: ath12k: enable ath12k AHB support Raj Kumar Bhagat
2025-03-25 14:57 ` [PATCH ath-next v12 00/13] wifi: ath12k: add Ath12k AHB driver support for IPQ5332 Jeff Johnson
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=72e9ddb1-c0eb-4eea-aa11-3f24ed0caea2@oss.qualcomm.com \
--to=jeff.johnson@oss.qualcomm.com \
--cc=ath12k@lists.infradead.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jjohnson@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_rajkbhag@quicinc.com \
--cc=robh@kernel.org \
--cc=vasanthakumar.thiagarajan@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