From: Kalle Valo <kvalo@codeaurora.org>
To: John Crispin <john@phrozen.org>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Miles Hu <milehu@codeaurora.org>,
linux-wireless@vger.kernel.org, ath11k@lists.infradead.org
Subject: Re: [PATCH V3 3/3] ath11k: add support for setting fixed HE rate/gi/ltf
Date: Thu, 30 Apr 2020 11:46:16 +0300 [thread overview]
Message-ID: <877dxxfjjb.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20200429145708.25992-3-john@phrozen.org> (John Crispin's message of "Wed, 29 Apr 2020 16:57:08 +0200")
John Crispin <john@phrozen.org> writes:
> From: Miles Hu <milehu@codeaurora.org>
>
> This patch adds ath11k support for setting fixed HE rate/gi/ltf values that
> we are now able to send to the kernel using nl80211. The added code is
> reusing parts of the existing code path already used for HT/VHT. The new
> helpers are symmetric to how we do it for HT/VHT.
>
> Signed-off-by: Miles Hu <milehu@codeaurora.org>
> Signed-off-by: John Crispin <john@phrozen.org>
[...]
> + if (he_ltf != 0xFF) {
> + vdev_param = WMI_VDEV_PARAM_HE_LTF;
> + /* start from 1 */
> + he_ltf += 1;
Indentation looks weird here, but I can fix that during commit.
--
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2020-04-30 8:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 14:57 [PATCH V3 1/3] nl80211: add support for setting fixed HE rate/gi/ltf John Crispin
2020-04-29 14:57 ` [PATCH V3 2/3] mac80211: " John Crispin
2020-04-29 14:57 ` [PATCH V3 3/3] ath11k: " John Crispin
2020-04-30 8:46 ` Kalle Valo [this message]
2020-05-01 2:14 ` kbuild test robot
2020-05-01 2:14 ` [RFC PATCH] ath11k: ath11k_mac_get_tx_mcs_map() can be static kbuild test robot
2020-04-30 22:38 ` [PATCH V3 1/3] nl80211: add support for setting fixed HE rate/gi/ltf kbuild test robot
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=877dxxfjjb.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=johannes@sipsolutions.net \
--cc=john@phrozen.org \
--cc=linux-wireless@vger.kernel.org \
--cc=milehu@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;
as well as URLs for NNTP newsgroup(s).