From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: "Rafał Miłecki" <zajec5@gmail.com>, "Kalle Valo" <kvalo@codeaurora.org>
Cc: "Franky Lin" <franky.lin@broadcom.com>,
"Hante Meuleman" <hante.meuleman@broadcom.com>,
"Chi-Hsien Lin" <chi-hsien.lin@cypress.com>,
"Wright Feng" <wright.feng@cypress.com>,
"Pieter-Paul Giesberts" <pieter-paul.giesberts@broadcom.com>,
"Chung-Hsien Hsu" <stanley.hsu@cypress.com>,
linux-wireless@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com,
brcm80211-dev-list@cypress.com,
"Rafał Miłecki" <rafal@milecki.pl>
Subject: Re: [PATCH] brcmfmac: update STA info struct to the v5
Date: Sat, 30 Jun 2018 20:48:43 +0200 [thread overview]
Message-ID: <5B37D08B.9050008@broadcom.com> (raw)
In-Reply-To: <20180628103623.29103-1-zajec5@gmail.com>
On 6/28/2018 12:36 PM, Rafał Miłecki wrote:
> From: Rafał Miłecki <rafal@milecki.pl>
>
> That struct is used when querying firmware for the STA. It seem is has
> been changing during the time. Luckily its format seems to be backward
> compatible starting with v2 (the only breakage was v1 -> v2).
>
> The version that was supported by brcmfmac so far was v4. It was what
> 43602a1 and 4366b1 firmwares (7.35.177.56 and 10.10.69.3309 accordingly)
> were using. It also seems to be used by early 4366c0 firmwares
> (10.10.69.6908 and 10.10.69.69017).
>
> The problem appears when switching to the 10.10.122.20 firmware. It uses
> v5 and instead of falling back to v4 when submitted buffer isn't big
> enough it fallbacks to the v3.
>
> To receive all v4 specific info with the newest firmware we have to
> submit a struct (buffer) that matches v5.
So do you have firmware that actually return v5 in the 'ver' field. I am
asking because I see a comment that version 5 is obsoleted and in recent
branch we are at version 7. Just curious what the actual version is. If
you do not explicitly need version 5 I would prefer to skip it and move
to version 6 struct. Otherwise it is...
Acked-by: Arend van Spriel <arend.vanspriel@broadcom.com>
> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
> ---
> .../net/wireless/broadcom/brcm80211/brcmfmac/fwil_types.h | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/fwil_types.h b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/fwil_types.h
> index 9b3a58e89dd1..d5bb81e88762 100644
> --- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/fwil_types.h
> +++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/fwil_types.h
> @@ -174,6 +174,8 @@
> #define BRCMF_MFP_CAPABLE 1
> #define BRCMF_MFP_REQUIRED 2
>
> +#define BRCMF_VHT_CAP_MCS_MAP_NSS_MAX 8
> +
> /* MAX_CHUNK_LEN is the maximum length for data passing to firmware in each
> * ioctl. It is relatively small because firmware has small maximum size input
> * playload restriction for ioctls.
> @@ -550,6 +552,8 @@ struct brcmf_sta_info_le {
> /* w/hi bit set if basic */
> __le32 in; /* seconds elapsed since associated */
> __le32 listen_interval_inms; /* Min Listen interval in ms for STA */
> +
> + /* Fields valid for ver >= 3 */
> __le32 tx_pkts; /* # of packets transmitted */
> __le32 tx_failures; /* # of packets failed */
> __le32 rx_ucast_pkts; /* # of unicast packets received */
> @@ -558,6 +562,8 @@ struct brcmf_sta_info_le {
> __le32 rx_rate; /* Rate of last successful rx frame */
> __le32 rx_decrypt_succeeds; /* # of packet decrypted successfully */
> __le32 rx_decrypt_failures; /* # of packet decrypted failed */
> +
> + /* Fields valid for ver >= 4 */
> __le32 tx_tot_pkts; /* # of tx pkts (ucast + mcast) */
> __le32 rx_tot_pkts; /* # of data packets recvd (uni + mcast) */
> __le32 tx_mcast_pkts; /* # of mcast pkts txed */
> @@ -594,6 +600,14 @@ struct brcmf_sta_info_le {
> */
> __le32 rx_pkts_retried; /* # rx with retry bit set */
> __le32 tx_rate_fallback; /* lowest fallback TX rate */
> +
> + /* Fields valid for ver >= 5 */
> + struct {
> + __le32 count; /* # rates in this set */
> + u8 rates[BRCMF_MAXRATES_IN_SET]; /* rates in 500kbps units w/hi bit set if basic */
> + u8 mcs[BRCMF_MCSSET_LEN]; /* supported mcs index bit map */
> + __le16 vht_mcs[BRCMF_VHT_CAP_MCS_MAP_NSS_MAX]; /* supported mcs index bit map per nss */
> + } rateset_adv;
> };
>
> struct brcmf_chanspec_list {
>
next prev parent reply other threads:[~2018-06-30 18:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 10:36 [PATCH] brcmfmac: update STA info struct to the v5 Rafał Miłecki
2018-06-30 18:48 ` Arend van Spriel [this message]
2018-07-01 6:01 ` Rafał Miłecki
2018-07-04 15:08 ` Kalle Valo
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=5B37D08B.9050008@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211-dev-list@cypress.com \
--cc=chi-hsien.lin@cypress.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pieter-paul.giesberts@broadcom.com \
--cc=rafal@milecki.pl \
--cc=stanley.hsu@cypress.com \
--cc=wright.feng@cypress.com \
--cc=zajec5@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.