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 v2] ath: use PRI value given by spec for fixed PRI
Date: Sun, 27 Sep 2015 15:53:15 +0300 [thread overview]
Message-ID: <87fv20c9c4.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <f2542c539e8c0eab1b0cbd184dceeb412a3e4516.1441821191.git.poh@qca.qualcomm.com> (Peter Oh's message of "Wed, 9 Sep 2015 10:53:23 -0700")
Peter Oh <poh@qca.qualcomm.com> writes:
> PRI value is used as divider when DFS detector analyzes candidate
> radar pulses.
> If PRI deviation is big from its origin PRI, DFS detector could miss
> valid radar reports since HW often misses detecting radar pulses and
> causes long interval value of pulses.
>
> For instance from practical results, if runtime PRI is calculated as
> 1431 for fixed PRI value of 1428 and delta timestamp logs 15719,
> the modular remainder will be 1409 and the delta between the remainder
> and runtime PRI is 22 that is bigger than PRI tolerance which is 16.
> As a result this radar report will be ignored even though it's valid.
>
> By using spec defined PRI for fixed PRI, we can correct this error.
>
> 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 v2] ath: use PRI value given by spec for fixed PRI
Date: Sun, 27 Sep 2015 15:53:15 +0300 [thread overview]
Message-ID: <87fv20c9c4.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <f2542c539e8c0eab1b0cbd184dceeb412a3e4516.1441821191.git.poh@qca.qualcomm.com> (Peter Oh's message of "Wed, 9 Sep 2015 10:53:23 -0700")
Peter Oh <poh@qca.qualcomm.com> writes:
> PRI value is used as divider when DFS detector analyzes candidate
> radar pulses.
> If PRI deviation is big from its origin PRI, DFS detector could miss
> valid radar reports since HW often misses detecting radar pulses and
> causes long interval value of pulses.
>
> For instance from practical results, if runtime PRI is calculated as
> 1431 for fixed PRI value of 1428 and delta timestamp logs 15719,
> the modular remainder will be 1409 and the delta between the remainder
> and runtime PRI is 22 that is bigger than PRI tolerance which is 16.
> As a result this radar report will be ignored even though it's valid.
>
> By using spec defined PRI for fixed PRI, we can correct this error.
>
> Signed-off-by: Peter Oh <poh@qca.qualcomm.com>
Thanks, applied.
--
Kalle Valo
next prev parent reply other threads:[~2015-09-27 12:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-09 17:53 [PATCH v2] ath: use PRI value given by spec for fixed PRI Peter Oh
2015-09-09 17:53 ` Peter Oh
2015-09-27 12:53 ` Kalle Valo [this message]
2015-09-27 12:53 ` Kalle Valo
-- strict thread matches above, loose matches on Subject: below --
2015-09-08 17:04 Peter Oh
2015-09-08 17:04 ` Peter Oh
2015-09-09 9:55 ` Kalle Valo
2015-09-09 9:55 ` 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=87fv20c9c4.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.