ATH11K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Venkateswara Naralasetty <quic_vnaralas@quicinc.com>,
	 ath11k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCHv2 1/6] nl80211: vendor-cmd: qca: add command for CFR configuration
Date: Fri, 11 Mar 2022 12:04:28 +0100	[thread overview]
Message-ID: <623add710d06dfd90291cb788756d37046ea2c74.camel@sipsolutions.net> (raw)
In-Reply-To: <1645005922-7252-2-git-send-email-quic_vnaralas@quicinc.com>

On Wed, 2022-02-16 at 15:35 +0530, Venkateswara Naralasetty wrote:
> Channel Frequency Response feature is to get the channel state
> information from the hardware based on the user configurations
> and send the CSI data to user space.
> 
> CSI data is further processed in user space which can be used to
> identify the motion of the objects.
> 
> Add vendor command support to configure per peer CFR parameters.
> 
> An example of usage:
> iw dev wlanx vendor send 0x1374 0xad cfr-en <val> bw <bw> method <method>
> periodicity <period> addr <mac_addr>
> 
> 0x1374: vendor id
> 0xad: : vendor subcmd id
> val: 0 to disable CFR capture
>      1 to enable CFR capture
> 
> bw: CFR capture bandwidth(use the values in enum nl80211_chan_width)
> 	1 - 20MHZ
> 	2 - 40MHZ
> 	3 - 80MHZ
> 
> method: Method used by hardware to collect the CFR dump
> 	0 - from the ACKs of QOS NULL packets
> 	1 - from the ACKs of QOS NULL packets with phase
> 	2 - from the ACK of probe response packet
> 
> periodicity: Periodicity in ms at which CFR dump need to be collect
> 	0 - single shot capture
> 	non zero - for Periodic captures
> 
> mac_addr: mac address of the peer for which CFR capture is requested.
> 
> Signed-off-by: Venkateswara Naralasetty <quic_vnaralas@quicinc.com>
> ---
> v2:
>  * Updated the commit log.
> 

That's a bit better, thanks.

However, it still doesn't address the question of why it needs to be
vendor specific API.

Is this something fundamentally tied to the hardware? Fundamentally
vendor specific? I'm not sure I see why it would be?

johannes

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

  reply	other threads:[~2022-03-11 11:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-16 10:05 [PATCHv2 0/6] ath11k: add single shot/periodic CFR capture support for IPQ8074 Venkateswara Naralasetty
2022-02-16 10:05 ` [PATCHv2 1/6] nl80211: vendor-cmd: qca: add command for CFR configuration Venkateswara Naralasetty
2022-03-11 11:04   ` Johannes Berg [this message]
2022-03-15 11:56     ` Venkateswara Naralasetty (QUIC)
2022-02-16 10:05 ` [PATCHv2 2/6] ath11k: CFR module initialization and deinitialization for IPQ8074 Venkateswara Naralasetty
2022-02-16 10:05 ` [PATCHv2 3/6] ath11k: register relayfs entries for CFR dump Venkateswara Naralasetty
2022-02-16 10:05 ` [PATCHv2 4/6] ath11k: register vendor sub command for CFR configuration Venkateswara Naralasetty
2022-02-16 10:05 ` [PATCHv2 5/6] ath11k: Register DBR event handler for CFR data Venkateswara Naralasetty
2022-02-16 10:05 ` [PATCHv2 6/6] ath11k: Register handler for CFR capture event Venkateswara Naralasetty

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=623add710d06dfd90291cb788756d37046ea2c74.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=ath11k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=quic_vnaralas@quicinc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox