From: Kalle Valo <kvalo@codeaurora.org>
To: Sriram R <srirrama@codeaurora.org>
Cc: ath11k@lists.infradead.org
Subject: Re: [PATCH] ath11k: Fix warnings that trigger during peer assoc when fixed rate is set
Date: Thu, 18 Jul 2019 11:19:44 +0000 (UTC) [thread overview]
Message-ID: <20190718111944.BA7F860E3F@smtp.codeaurora.org> (raw)
In-Reply-To: <1563288088-2821-1-git-send-email-srirrama@codeaurora.org>
Sriram R <srirrama@codeaurora.org> wrote:
> When VHT fixed rate is set to MCS < 7, warnings are seen when a new sta
> gets associated while peer_assoc command is sent to firmware. This is
> seen since we expect tx_mcs_set sent to firmware as values corresponding
> to range 0-7, 0-8 or 0-9. Since the intersection of STA's VHT MCS support
> and current bitrate mask after fixed rate is set has MCS < 7 warning is
> thrown currently.
> Remove these warning for these cases as it's a valid scenario.
> For these cases, 0-7 MCS can be sent during peer assoc to firmware as
> this is followed by peer fixed rate setting.
>
> Signed-off-by: Sriram R <srirrama@codeaurora.org>
> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Patch applied to ath11k-bringup branch of ath.git, thanks.
2d7490549ec1 ath11k: Fix warnings that trigger during peer assoc when fixed rate is set
--
https://patchwork.kernel.org/patch/11046187/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
prev parent reply other threads:[~2019-07-18 11:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-16 14:41 [PATCH] ath11k: Fix warnings that trigger during peer assoc when fixed rate is set Sriram R
2019-07-18 11:19 ` Kalle Valo [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=20190718111944.BA7F860E3F@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=srirrama@codeaurora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox