Linux wireless drivers development
 help / color / mirror / Atom feed
From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: ath12k@lists.infradead.org,
	Aaradhana Sahu <aaradhana.sahu@oss.qualcomm.com>
Cc: linux-wireless@vger.kernel.org, jjohnson@kernel.org,
	quic_kiranv@quicinc.com, baochen.qiang@oss.qualcomm.com,
	vasanthakumar.thiagarajan@oss.qualcomm.com
Subject: Re: [PATCH ath-next] wifi: ath12k: add support to load shared firmware on multiPD
Date: Thu, 10 Sep 2026 14:31:50 -0700	[thread overview]
Message-ID: <178907591083.684897.6314733930806411528.b4-ty@oss.qualcomm.com> (raw)
In-Reply-To: <20260811054316.518494-1-aaradhana.sahu@oss.qualcomm.com>


On Tue, 11 Aug 2026 11:13:16 +0530, Aaradhana Sahu wrote:
> IPQ5332 platform uses a MultiPD architecture where multiple firmware
> instances share common read-only code segments. The driver currently
> loads only the per-UserPD firmware, which leaves the shared read-only
> firmware unloaded.
> 
> Add support for loading the shared read-only firmware once before the
> UserPDs are powered up. The shared segment contains common code that is
> identical across all UserPDs and reduces the total firmware memory
> requirement.
> 
> [...]

Applied, thanks!

[1/1] wifi: ath12k: add support to load shared firmware on multiPD
      commit: c3bace8584ca707e34ba837f65c2e9d566af4c2c

Best regards,
-- 
Jeff Johnson <jeff.johnson@oss.qualcomm.com>


      parent reply	other threads:[~2026-09-10 21:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-11  5:43 [PATCH ath-next] wifi: ath12k: add support to load shared firmware on multiPD Aaradhana Sahu
2026-08-11  9:08 ` Vasanthakumar Thiagarajan
2026-08-12 13:57   ` Jeff Johnson
2026-08-12  2:03 ` Baochen Qiang
2026-08-14 18:24 ` Jeff Johnson
2026-08-17  6:10   ` Aaradhana Sahu
2026-09-10 21:31 ` Jeff Johnson [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=178907591083.684897.6314733930806411528.b4-ty@oss.qualcomm.com \
    --to=jeff.johnson@oss.qualcomm.com \
    --cc=aaradhana.sahu@oss.qualcomm.com \
    --cc=ath12k@lists.infradead.org \
    --cc=baochen.qiang@oss.qualcomm.com \
    --cc=jjohnson@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=quic_kiranv@quicinc.com \
    --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