From: Baochen Qiang <baochen.qiang@oss.qualcomm.com>
To: "Yu Zhang(Yuriy)" <yu.zhang@oss.qualcomm.com>, jjohnson@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
ath11k@lists.infradead.org
Subject: Re: [PATCH ath-next 1/6] wifi: ath11k: Add initialization and deinitialization sequence for CFR module
Date: Fri, 31 Oct 2025 10:42:45 +0800 [thread overview]
Message-ID: <ba928aa0-d1d0-4e10-bfd4-ab7a577dc8c1@oss.qualcomm.com> (raw)
In-Reply-To: <20251030043150.3905086-2-yu.zhang@oss.qualcomm.com>
On 10/30/2025 12:31 PM, Yu Zhang(Yuriy) wrote:
> +void ath11k_cfr_deinit(struct ath11k_base *ab)
> +{
> + struct ath11k_pdev *pdev;
> + struct ath11k_cfr *cfr;
> + struct ath11k *ar;
> + int i;
> +
> + if (!test_bit(WMI_TLV_SERVICE_CFR_CAPTURE_SUPPORT, ab->wmi_ab.svc_map) ||
> + !ab->hw_params.cfr_support)
> + return;
> +
> + for (i = 0; i < ab->num_radios; i++) {
> + pdev = rcu_dereference(ab->pdevs_active[i]);
_deinit() runs during driver unload etc where pdev may not be active hence issues can be
expected?
besides, pdevs_active used here but pdev used in _init() ...
IMO, we don't need pdev to be active here
> + if (pdev && pdev->ar) {
> + ar = ab->pdevs[i].ar;
> + cfr = &ar->cfr;
> +
> + ath11k_cfr_ring_free(ar);
> +
> + spin_lock_bh(&cfr->lut_lock);
> + kfree(cfr->lut);
> + cfr->lut = NULL;
> + spin_unlock_bh(&cfr->lut_lock);
> + }
> + }
> +}
> +
> +int ath11k_cfr_init(struct ath11k_base *ab)
> +{
> + struct ath11k_dbring_cap db_cap;
> + struct ath11k_cfr *cfr;
> + u32 num_lut_entries;
> + struct ath11k *ar;
> + int i, ret;
> +
> + if (!test_bit(WMI_TLV_SERVICE_CFR_CAPTURE_SUPPORT, ab->wmi_ab.svc_map) ||
> + !ab->hw_params.cfr_support)
> + return 0;
> +
> + for (i = 0; i < ab->num_radios; i++) {
> + ar = ab->pdevs[i].ar;
> + cfr = &ar->cfr;
> +
> + ret = ath11k_dbring_get_cap(ar->ab, ar->pdev_idx,
> + WMI_DIRECT_BUF_CFR, &db_cap);
> + if (ret)
> + continue;
> +
> + idr_init(&cfr->rx_ring.bufs_idr);
> + spin_lock_init(&cfr->rx_ring.idr_lock);
> + spin_lock_init(&cfr->lock);
> + spin_lock_init(&cfr->lut_lock);
> +
> + num_lut_entries = min_t(u32, CFR_MAX_LUT_ENTRIES, db_cap.min_elem);
> + cfr->lut = kcalloc(num_lut_entries, sizeof(*cfr->lut),
> + GFP_KERNEL);
> + if (!cfr->lut) {
> + ret = -ENOMEM;
> + goto err;
> + }
> +
> + ret = ath11k_cfr_ring_alloc(ar, &db_cap);
> + if (ret) {
> + ath11k_warn(ab, "failed to init cfr ring for pdev %d: %d\n",
> + i, ret);
> + goto err;
you need to free lut before jumping to error handling
> + }
> +
> + cfr->lut_num = num_lut_entries;
> + }
> +
> + return 0;
> +
> +err:
> + for (i = i - 1; i >= 0; i--) {
> + ar = ab->pdevs[i].ar;
> + cfr = &ar->cfr;
> +
> + ath11k_cfr_ring_free(ar);
> +
> + spin_lock_bh(&cfr->lut_lock);
> + kfree(cfr->lut);
> + cfr->lut = NULL;
> + spin_unlock_bh(&cfr->lut_lock);
> + }
> + return ret;
> +}
next prev parent reply other threads:[~2025-10-31 2:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 4:31 [PATCH ath-next 0/6] wifi: ath11k: Add single shot/periodic CFR capture support Yu Zhang(Yuriy)
2025-10-30 4:31 ` [PATCH ath-next 1/6] wifi: ath11k: Add initialization and deinitialization sequence for CFR module Yu Zhang(Yuriy)
2025-10-31 2:42 ` Baochen Qiang [this message]
2025-10-30 4:31 ` [PATCH ath-next 2/6] wifi: ath11k: Register debugfs for CFR configuration Yu Zhang(Yuriy)
2025-10-31 2:43 ` Baochen Qiang
2025-11-02 9:21 ` Yu Zhang(Yuriy)
2025-11-03 3:14 ` Baochen Qiang
2025-11-03 7:37 ` Yu Zhang(Yuriy)
2025-10-30 4:31 ` [PATCH ath-next 3/6] wifi: ath11k: Add support unassociated client CFR Yu Zhang(Yuriy)
2025-10-30 4:31 ` [PATCH ath-next 4/6] wifi: ath11k: Register relayfs entries for CFR dump Yu Zhang(Yuriy)
2025-10-30 4:31 ` [PATCH ath-next 5/6] wifi: ath11k: Register DBR event handler for CFR data Yu Zhang(Yuriy)
2025-10-31 2:59 ` Baochen Qiang
2025-10-30 4:31 ` [PATCH ath-next 6/6] wifi: ath11k: Register handler for CFR capture event Yu Zhang(Yuriy)
2025-10-31 3:05 ` Baochen Qiang
2025-10-30 18:17 ` [PATCH ath-next 0/6] wifi: ath11k: Add single shot/periodic CFR capture support Vasanthakumar Thiagarajan
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=ba928aa0-d1d0-4e10-bfd4-ab7a577dc8c1@oss.qualcomm.com \
--to=baochen.qiang@oss.qualcomm.com \
--cc=ath11k@lists.infradead.org \
--cc=jjohnson@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=yu.zhang@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