All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Peter Oh <peter.oh@bowerswilkins.com>
Cc: linux-wireless@vger.kernel.org,
	Sriram R <srirrama@codeaurora.org>,
	ath10k@lists.infradead.org
Subject: Re: [PATCH 1/2] ath: Add support to get the detected radar specifications
Date: Mon, 14 May 2018 17:51:04 +0300	[thread overview]
Message-ID: <871sees33b.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <cf60f81c-9466-ac52-e902-413fe3163490@bowerswilkins.com> (Peter Oh's message of "Mon, 30 Apr 2018 12:01:45 -0700")

Peter Oh <peter.oh@bowerswilkins.com> writes:

> On 04/30/2018 10:45 AM, Sriram R wrote:
>> This enables ath10k/ath9k drivers to collect the specifications of the
>> radar type once it is detected by the dfs pattern detector unit.
>> Usage of the collected info is specific to driver implementation.
>> For example, collected radar info could be used by the host driver
>> to send to co-processors for additional processing/validation.
>
> What kind of additional processing/validation does it do?
> Please give us more details for that.

This is handled in patch 2.

-- 
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@codeaurora.org>
To: Peter Oh <peter.oh@bowerswilkins.com>
Cc: Sriram R <srirrama@codeaurora.org>,
	ath10k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/2] ath: Add support to get the detected radar specifications
Date: Mon, 14 May 2018 17:51:04 +0300	[thread overview]
Message-ID: <871sees33b.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <cf60f81c-9466-ac52-e902-413fe3163490@bowerswilkins.com> (Peter Oh's message of "Mon, 30 Apr 2018 12:01:45 -0700")

Peter Oh <peter.oh@bowerswilkins.com> writes:

> On 04/30/2018 10:45 AM, Sriram R wrote:
>> This enables ath10k/ath9k drivers to collect the specifications of the
>> radar type once it is detected by the dfs pattern detector unit.
>> Usage of the collected info is specific to driver implementation.
>> For example, collected radar info could be used by the host driver
>> to send to co-processors for additional processing/validation.
>
> What kind of additional processing/validation does it do?
> Please give us more details for that.

This is handled in patch 2.

-- 
Kalle Valo

  reply	other threads:[~2018-05-14 14:51 UTC|newest]

Thread overview: 38+ 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 ` Sriram R
2018-04-30 17:45 ` [PATCH 1/2] ath: Add support to get the detected radar specifications Sriram R
2018-04-30 17:45   ` Sriram R
2018-04-30 19:01   ` Peter Oh
2018-04-30 19:01     ` Peter Oh
2018-05-14 14:51     ` Kalle Valo [this message]
2018-05-14 14:51       ` Kalle Valo
2018-04-30 17:45 ` [PATCH 2/2] ath10k: DFS Host Confirmation Sriram R
2018-04-30 17:45   ` Sriram R
2018-04-30 19:50   ` Peter Oh
2018-04-30 19:50     ` Peter Oh
2018-05-02 11:27     ` Kalle Valo
2018-05-02 11:27       ` Kalle Valo
2018-05-03  6:25       ` Peter Oh
2018-05-03  6:25         ` Peter Oh
2018-05-14 18:10         ` Kalle Valo
2018-05-14 18:10           ` Kalle Valo
2018-05-14 20:55           ` Peter Oh
2018-05-14 20:55             ` Peter Oh
2018-05-05  9:45       ` Sebastian Gottschall
2018-05-05  9:45         ` Sebastian Gottschall
2018-05-09 10:45     ` Sriram R
2018-05-09 10:45       ` Sriram R
2018-05-03 23:48   ` Adrian Chadd
2018-05-03 23:48     ` Adrian Chadd
2018-05-14 18:25     ` Kalle Valo
2018-05-14 18:25       ` Kalle Valo
2018-05-14 21:13       ` Adrian Chadd
2018-05-14 21:13         ` Adrian Chadd
2018-05-15  5:04         ` Kalle Valo
2018-05-15  5:04           ` Kalle Valo
2018-05-15 18:59           ` Peter Oh
2018-05-15 18:59             ` Peter Oh
2018-05-16 10:09             ` Kalle Valo
2018-05-16 10:09               ` Kalle Valo
2018-05-12  9:57   ` Kalle Valo
2018-05-12  9:57     ` 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=871sees33b.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@codeaurora.org \
    --cc=ath10k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=peter.oh@bowerswilkins.com \
    --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.