From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: kvalo@codeaurora.org, linux-wireless@vger.kernel.org,
wcn36xx@lists.infradead.org, linux-arm-msm@vger.kernel.org
Cc: loic.poulain@linaro.org, benl@squareup.com, bryan.odonoghue@linaro.org
Subject: [PATCH v2 0/3] wcn36xx: Implement explicit beacon filter tables
Date: Mon, 13 Dec 2021 15:00:28 +0000 [thread overview]
Message-ID: <20211213150031.1707955-1-bryan.odonoghue@linaro.org> (raw)
V2:
Removes duplicate defintion of mask field defines
V1:
Downstream provides the ability to directly program the beacon filter
tables. Currently in upstream we rely on whatever is the default filtration
table in firmware.
A trivial packing fixup is required for the SMD structure. The downstream
filtration table from the Linux driver is applied but, we are not
necessarily constrained to using this table forever.
Tested on wcn3620 and wcn3680b.
Bryan O'Donoghue (3):
wcn36xx: Fix beacon filter structure definitions
wcn36xx: Fix physical location of beacon filter comment
wcn36xx: Implement downstream compliant beacon filtering
drivers/net/wireless/ath/wcn36xx/hal.h | 30 +++++++--
drivers/net/wireless/ath/wcn36xx/main.c | 1 +
drivers/net/wireless/ath/wcn36xx/smd.c | 87 +++++++++++++++++++++++++
drivers/net/wireless/ath/wcn36xx/smd.h | 3 +
4 files changed, 115 insertions(+), 6 deletions(-)
--
2.33.0
next reply other threads:[~2021-12-13 14:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-13 15:00 Bryan O'Donoghue [this message]
2021-12-13 15:00 ` [PATCH v2 1/3] wcn36xx: Fix beacon filter structure definitions Bryan O'Donoghue
2021-12-13 15:00 ` [PATCH v2 2/3] wcn36xx: Fix physical location of beacon filter comment Bryan O'Donoghue
2021-12-13 15:00 ` [PATCH v2 3/3] wcn36xx: Implement downstream compliant beacon filtering Bryan O'Donoghue
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=20211213150031.1707955-1-bryan.odonoghue@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=benl@squareup.com \
--cc=kvalo@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=wcn36xx@lists.infradead.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 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.