From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Peter Oh <poh@qca.qualcomm.com>
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH] ath: support new FCC DFS Radar Type 1
Date: Wed, 15 Apr 2015 15:00:45 +0300 [thread overview]
Message-ID: <87sic17g9e.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1427305036-20326-1-git-send-email-poh@qca.qualcomm.com> (Peter Oh's message of "Wed, 25 Mar 2015 10:37:16 -0700")
Peter Oh <poh@qca.qualcomm.com> writes:
> Add support for new FCC DFS rules released on August 14, 2014.
> FCC has added a new radar type named Radar Type 1 and original
> Radar Type 1 is renamed to Radar Type 0 in consequence.
>
> During the certificate test, Type 1 PRI values are randomly selected
> within the range of 518 and 3066 and we divide it to 3 groups based on
> practical test result data collected for more than a year.
>
> For about Radar type ID, it does nothing to functionalities.
> In other words, even if we re-order the IDs, DFS detection will
> work as well, but we give the ID with matching to FCC doc.
>
> By adding this support, the drivers using this DFS function are
> able to support both of old and new FCC DFS rules simultaneously
> without any other changes.
>
> Signed-off-by: Peter Oh <poh@qca.qualcomm.com>
Thanks, applied.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Peter Oh <poh@qca.qualcomm.com>
Cc: <ath10k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] ath: support new FCC DFS Radar Type 1
Date: Wed, 15 Apr 2015 15:00:45 +0300 [thread overview]
Message-ID: <87sic17g9e.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1427305036-20326-1-git-send-email-poh@qca.qualcomm.com> (Peter Oh's message of "Wed, 25 Mar 2015 10:37:16 -0700")
Peter Oh <poh@qca.qualcomm.com> writes:
> Add support for new FCC DFS rules released on August 14, 2014.
> FCC has added a new radar type named Radar Type 1 and original
> Radar Type 1 is renamed to Radar Type 0 in consequence.
>
> During the certificate test, Type 1 PRI values are randomly selected
> within the range of 518 and 3066 and we divide it to 3 groups based on
> practical test result data collected for more than a year.
>
> For about Radar type ID, it does nothing to functionalities.
> In other words, even if we re-order the IDs, DFS detection will
> work as well, but we give the ID with matching to FCC doc.
>
> By adding this support, the drivers using this DFS function are
> able to support both of old and new FCC DFS rules simultaneously
> without any other changes.
>
> Signed-off-by: Peter Oh <poh@qca.qualcomm.com>
Thanks, applied.
--
Kalle Valo
next prev parent reply other threads:[~2015-04-15 12:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-25 17:37 [PATCH] ath: support new FCC DFS Radar Type 1 Peter Oh
2015-03-25 17:37 ` Peter Oh
2015-04-15 12:00 ` Kalle Valo [this message]
2015-04-15 12:00 ` Kalle Valo
-- strict thread matches above, loose matches on Subject: below --
2015-02-25 22:17 Peter Oh
2015-02-25 22:17 ` Peter Oh
2015-02-27 10:45 ` Zefir Kurtisi
2015-02-27 10:45 ` Zefir Kurtisi
2015-03-03 1:29 ` Peter Oh
2015-03-03 1:29 ` Peter Oh
2015-03-03 1:48 ` Peter Oh
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=87sic17g9e.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=poh@qca.qualcomm.com \
/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.