From: Vasanthakumar Thiagarajan <vasanthakumar.thiagarajan@oss.qualcomm.com>
To: Raj Kumar Bhagat <quic_rajkbhag@quicinc.com>, ath12k@lists.infradead.org
Cc: 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>,
linux-wireless@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Sowmiya Sree Elavalagan <quic_ssreeela@quicinc.com>
Subject: Re: [PATCH ath-next v11 11/13] wifi: ath12k: Power up userPD
Date: Tue, 18 Mar 2025 09:31:30 +0530 [thread overview]
Message-ID: <37a33341-a83f-6349-6bff-23b082aa46ad@oss.qualcomm.com> (raw)
In-Reply-To: <20250317204639.1864742-12-quic_rajkbhag@quicinc.com>
On 3/18/2025 2:16 AM, Raj Kumar Bhagat wrote:
> From: Sowmiya Sree Elavalagan <quic_ssreeela@quicinc.com>
>
> UserPD firmware image is loaded and booted by ath12k driver. Get the userPD
> memory region from DTS and load the firmware for userPD from pre-defined
> path into io-remapped address of this region. Authenticate this image
> using pasid which is a peripheral ID. Set the spawn bit to instruct Q6
> to spawn userPD thread. Wait for userPD to spawn which is indicated by
> spawn interrupt. Ready interrupt is triggered once the userPD is powered
> up completely.
>
> Tested-on: IPQ5332 hw1.0 AHB WLAN.WBE.1.3.1-00130-QCAHKSWPL_SILICONZ-1
>
> Signed-off-by: Sowmiya Sree Elavalagan <quic_ssreeela@quicinc.com>
> Signed-off-by: Raj Kumar Bhagat <quic_rajkbhag@quicinc.com>
Reviewed-by: Vasanthakumar Thiagarajan <vasanthakumar.thiagarajan@oss.qualcomm.com>
next prev parent reply other threads:[~2025-03-18 4:01 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-17 20:46 [PATCH ath-next v11 00/13] wifi: ath12k: add Ath12k AHB driver support for IPQ5332 Raj Kumar Bhagat
2025-03-17 20:46 ` [PATCH ath-next v11 01/13] dt-bindings: net: wireless: describe the ath12k AHB module " Raj Kumar Bhagat
2025-03-17 20:46 ` [PATCH ath-next v11 02/13] wifi: ath12k: fix incorrect CE addresses Raj Kumar Bhagat
2025-03-17 20:46 ` [PATCH ath-next v11 03/13] wifi: ath12k: refactor ath12k_hw_regs structure Raj Kumar Bhagat
2025-03-17 20:46 ` [PATCH ath-next v11 04/13] wifi: ath12k: add ath12k_hw_params for IPQ5332 Raj Kumar Bhagat
2025-03-17 20:46 ` [PATCH ath-next v11 05/13] wifi: ath12k: avoid m3 firmware download in AHB device IPQ5332 Raj Kumar Bhagat
2025-03-17 20:46 ` [PATCH ath-next v11 06/13] wifi: ath12k: Add hw_params to remap CE register space for IPQ5332 Raj Kumar Bhagat
2025-03-17 20:46 ` [PATCH ath-next v11 07/13] wifi: ath12k: add support for fixed QMI firmware memory Raj Kumar Bhagat
2025-03-17 20:46 ` [PATCH ath-next v11 08/13] wifi: ath12k: add AHB driver support for IPQ5332 Raj Kumar Bhagat
2025-03-18 15:44 ` Jeff Johnson
2025-03-18 15:50 ` Krzysztof Kozlowski
2025-03-18 17:55 ` Jeff Johnson
2025-03-18 18:16 ` Krzysztof Kozlowski
2025-03-18 18:19 ` Krzysztof Kozlowski
2025-03-18 18:53 ` Jeff Johnson
2025-03-18 19:06 ` Krzysztof Kozlowski
2025-03-18 20:03 ` Jeff Johnson
2025-03-21 10:05 ` Raj Kumar Bhagat
2025-03-17 20:46 ` [PATCH ath-next v11 09/13] wifi: ath12k: Power up root PD Raj Kumar Bhagat
2025-03-17 20:46 ` [PATCH ath-next v11 10/13] wifi: ath12k: Register various userPD interrupts and save SMEM entries Raj Kumar Bhagat
2025-03-17 20:46 ` [PATCH ath-next v11 11/13] wifi: ath12k: Power up userPD Raj Kumar Bhagat
2025-03-18 4:01 ` Vasanthakumar Thiagarajan [this message]
2025-03-17 20:46 ` [PATCH ath-next v11 12/13] wifi: ath12k: Power down userPD Raj Kumar Bhagat
2025-03-17 20:46 ` [PATCH ath-next v11 13/13] wifi: ath12k: enable ath12k AHB support Raj Kumar Bhagat
2025-03-18 4:02 ` Vasanthakumar Thiagarajan
2025-03-18 8:00 ` [PATCH ath-next v11 00/13] wifi: ath12k: add Ath12k AHB driver support for IPQ5332 Krzysztof Kozlowski
2025-03-21 10:07 ` Raj Kumar Bhagat
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=37a33341-a83f-6349-6bff-23b082aa46ad@oss.qualcomm.com \
--to=vasanthakumar.thiagarajan@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=quic_ssreeela@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