From: Peter Oh <peter.oh@bowerswilkins.com>
To: Sriram R <srirrama@codeaurora.org>,
Kalle Valo <kvalo@codeaurora.org>,
ath10k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: Fwd: Re: [PATCHv2 2/2] ath10k: DFS Host Confirmation
Date: Tue, 15 May 2018 12:26:34 -0700 [thread overview]
Message-ID: <cf2b6989-cd97-68c5-8e6a-1e0c80cb9c7d@bowerswilkins.com> (raw)
In-Reply-To: <72826487-2af6-3c16-e7f8-3b2592416f9d@bowerswilkins.com>
> + /* Even in case of radar detection failure we follow the same
> + * behaviour as if radar is detected i.e to switch to a different
> + * channel.
> + */
> + if (status_arg.status == WMI_HW_RADAR_DETECTED ||
> + status_arg.status == WMI_RADAR_DETECTION_FAIL)
> + ath10k_radar_detected(ar);
>
This behavior is different from what Kalle explained.
Failing verification of radar type by FW does not enforce stop DFS
channels from using.
Kalle?
WARNING: multiple messages have this Message-ID (diff)
From: Peter Oh <peter.oh@bowerswilkins.com>
To: Sriram R <srirrama@codeaurora.org>,
Kalle Valo <kvalo@codeaurora.org>,
ath10k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: Fwd: Re: [PATCHv2 2/2] ath10k: DFS Host Confirmation
Date: Tue, 15 May 2018 12:26:34 -0700 [thread overview]
Message-ID: <cf2b6989-cd97-68c5-8e6a-1e0c80cb9c7d@bowerswilkins.com> (raw)
In-Reply-To: <72826487-2af6-3c16-e7f8-3b2592416f9d@bowerswilkins.com>
> + /* Even in case of radar detection failure we follow the same
> + * behaviour as if radar is detected i.e to switch to a different
> + * channel.
> + */
> + if (status_arg.status == WMI_HW_RADAR_DETECTED ||
> + status_arg.status == WMI_RADAR_DETECTION_FAIL)
> + ath10k_radar_detected(ar);
>
This behavior is different from what Kalle explained.
Failing verification of radar type by FW does not enforce stop DFS
channels from using.
Kalle?
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2018-05-15 19:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 9:07 [PATCHv2 0/2] ath/ath10k: DFS Host Confirmation Sriram R
2018-05-15 9:07 ` [PATCHv2 1/2] ath: Add support to get the detected radar specifications Sriram R
2018-05-15 9:07 ` [PATCHv2 2/2] ath10k: DFS Host Confirmation Sriram R
2018-05-15 19:23 ` Peter Oh
2018-05-15 19:26 ` Peter Oh [this message]
2018-05-15 19:26 ` Fwd: " Peter Oh
2018-05-15 9:14 ` [PATCHv2 0/2] ath/ath10k: " Sriram R
2018-05-15 9:28 ` 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=cf2b6989-cd97-68c5-8e6a-1e0c80cb9c7d@bowerswilkins.com \
--to=peter.oh@bowerswilkins.com \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@codeaurora.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 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.