From: Kalle Valo <kvalo@codeaurora.org>
To: Sriram R <srirrama@codeaurora.org>
Cc: ath10k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 2/2] ath10k: DFS Host Confirmation
Date: Sat, 12 May 2018 12:57:35 +0300 [thread overview]
Message-ID: <87a7t5urg0.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1525110339-25326-3-git-send-email-srirrama@codeaurora.org> (Sriram R.'s message of "Mon, 30 Apr 2018 23:15:39 +0530")
Sriram R <srirrama@codeaurora.org> writes:
> In the 10.4-3.6 firmware branch there's a new DFS Host confirmation
> feature which is advertised using WMI_SERVICE_HOST_DFS_CHECK_SUPPORT flag.
>
> This new features enables the ath10k host to send information to the
> firmware on the specifications of detected radar type. This allows the
> firmware to validate if the host's radar pattern detector unit is
> operational and check if the radar information shared by host matches
> the radar pulses sent as phy error events from firmware. If the check
> fails the firmware won't allow use of DFS channels on AP mode when using
> FCC regulatory region.
>
> Supported Chipsets : QCA9984/QCA9888/QCA4019
> Firmware Version : 10.4-3.6-00104
>
> Signed-off-by: Sriram R <srirrama@codeaurora.org>
This introduces a new checkpatch warning:
drivers/net/wireless/ath/ath10k/wmi.c:3753: Please use a blank line after function/struct/union/enum declarations
--
Kalle Valo
prev parent reply other threads:[~2018-05-12 9:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-30 17:45 [PATCH 0/2] ath/ath10k: DFS Host Confirmation Sriram R
2018-04-30 17:45 ` [PATCH 1/2] ath: Add support to get the detected radar specifications Sriram R
2018-04-30 19:01 ` Peter Oh
2018-05-14 14:51 ` Kalle Valo
2018-04-30 17:45 ` [PATCH 2/2] ath10k: DFS Host Confirmation Sriram R
2018-04-30 19:50 ` Peter Oh
2018-05-02 11:27 ` Kalle Valo
2018-05-03 6:25 ` Peter Oh
2018-05-14 18:10 ` Kalle Valo
2018-05-14 20:55 ` Peter Oh
2018-05-05 9:45 ` Sebastian Gottschall
2018-05-09 10:45 ` Sriram R
2018-05-03 23:48 ` Adrian Chadd
2018-05-14 18:25 ` Kalle Valo
2018-05-14 21:13 ` Adrian Chadd
2018-05-15 5:04 ` Kalle Valo
2018-05-15 18:59 ` Peter Oh
2018-05-16 10:09 ` Kalle Valo
2018-05-12 9:57 ` 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=87a7t5urg0.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).