From: "Nemanov, Michael" <michael.nemanov@ti.com>
To: "Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>,
Kalle Valo <kvalo@kernel.org>
Cc: Johannes Berg <johannes.berg@intel.com>,
<linux-kernel@vger.kernel.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [EXTERNAL] [PATCH wireless-next 6/8] wifi: wlcore: add pn16 support
Date: Thu, 30 May 2024 11:06:40 +0300 [thread overview]
Message-ID: <e6ae6dfa-6554-4e88-abb0-31dbbd8df03f@ti.com> (raw)
In-Reply-To: <E1sBsy7-00E8vu-Nc@rmk-PC.armlinux.org.uk>
On 5/28/2024 12:18 PM, Russell King (Oracle) wrote:
[...]
>
> static int wlcore_fw_status(struct wl1271 *wl, struct wl_fw_status *status)
> {
> + struct wl12xx_vif *wlvifsta;
> + struct wl12xx_vif *wlvifap;
> struct wl12xx_vif *wlvif;
> u32 old_tx_blk_count = wl->tx_blocks_available;
> int avail, freed_blocks;
> @@ -410,23 +412,100 @@ static int wlcore_fw_status(struct wl1271 *wl, struct wl_fw_status *status)
> wl->tx_pkts_freed[i] = status->counters.tx_released_pkts[i];
> }
>
[...]
> for_each_set_bit(i, wl->links_map, wl->num_links) {
> + u16 diff16, sec_pn16;
> u8 diff, tx_lnk_free_pkts;
> +
> lnk = &wl->links[i];
>
> /* prevent wrap-around in freed-packets counter */
> tx_lnk_free_pkts = status->counters.tx_lnk_free_pkts[i];
> diff = (tx_lnk_free_pkts - lnk->prev_freed_pkts) & 0xff;
>
> - if (diff == 0)
> + if (diff) {
> + lnk->allocated_pkts -= diff;
> + lnk->prev_freed_pkts = tx_lnk_free_pkts;
> + }
> +
> + /* Get the current sec_pn16 value if present */
> + if (status->counters.tx_lnk_sec_pn16)
> + sec_pn16 = __le16_to_cpu(status->counters.tx_lnk_sec_pn16[i]);
> + else
> + sec_pn16 = 0;
> + /* prevent wrap-around in pn16 counter */
> + diff16 = (sec_pn16 - lnk->prev_sec_pn16) & 0xffff;
> +
> + /* FIXME: since free_pkts is a 8-bit counter of packets that
> + * rolls over, it can become zero. If it is zero, then we
> + * omit processing below. Is that really correct?
> + */
> + if (tx_lnk_free_pkts <= 0)
> continue;
>
The original code was
tx_lnk_free_pkts = status->counters.tx_lnk_free_pkts[i];
diff = (tx_lnk_free_pkts - lnk->prev_freed_pkts) & 0xff;
if (diff == 0)
continue;
I wonder if comparing tx_lnk_free_pkts to 0 was added intentionally?
This is monotonously incremented counter so 0 is not significant, unlike
the diff.
Have I missed something?
Michael.
next prev parent reply other threads:[~2024-05-30 8:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 9:17 [PATCH wireless-next 0/8] wifi: TI wilink8 updates Russell King (Oracle)
2024-05-28 9:17 ` [PATCH wireless-next 1/8] wifi: wlcore: correctness fix fwlog reading Russell King (Oracle)
2024-06-18 10:22 ` Kalle Valo
2024-05-28 9:17 ` [PATCH wireless-next 2/8] wifi: wl18xx: make wl18xx_tx_immediate_complete() more efficient Russell King (Oracle)
2024-05-28 9:17 ` [PATCH wireless-next 3/8] wifi: wlcore: improve code in wlcore_fw_status() Russell King (Oracle)
2024-05-28 9:17 ` [PATCH wireless-next 4/8] wifi: wlcore: pass "status" to wlcore_hw_convert_fw_status() Russell King (Oracle)
2024-05-29 13:15 ` Nemanov, Michael
2024-05-29 13:31 ` Russell King (Oracle)
2024-05-28 9:18 ` [PATCH wireless-next 5/8] wifi: wlcore: store AP encryption key type Russell King (Oracle)
2024-05-28 9:18 ` [PATCH wireless-next 6/8] wifi: wlcore: add pn16 support Russell King (Oracle)
2024-05-30 8:06 ` Nemanov, Michael [this message]
2024-05-30 8:20 ` [EXTERNAL] " Russell King (Oracle)
2024-05-30 12:25 ` Nemanov, Michael
2024-05-30 12:46 ` Nemanov, Michael
2024-05-28 9:18 ` [PATCH wireless-next 7/8] wifi: wl18xx: add support for reading 8.9.1 fw status Russell King (Oracle)
2024-05-28 9:18 ` [PATCH wireless-next 8/8] wifi: wl18xx: allow firmwares > 8.9.0.x.58 Russell King (Oracle)
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=e6ae6dfa-6554-4e88-abb0-31dbbd8df03f@ti.com \
--to=michael.nemanov@ti.com \
--cc=johannes.berg@intel.com \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rmk+kernel@armlinux.org.uk \
/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