From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: A good way to get CSI info to user-space?
Date: Mon, 23 Oct 2017 22:30:35 +0200 [thread overview]
Message-ID: <1508790635.2639.24.camel@sipsolutions.net> (raw)
In-Reply-To: <6f9182c4-cff9-066c-173a-00d09af7c903@candelatech.com> (sfid-20171023_195440_976958_B20E3A62)
Hi,
> I have been poking at ath10k to get some CSI reporting working.
> The CSI reports are a bit over 2k bytes in length, and they could
> happen quite often. As far as I can tell, there is no good way in
> the kernel to make this available.
>
> I was thinking maybe a callback into the mac80211 stack, which would
> then send a netlink event might be a useful way to implement this?
The CSI data has variable length [1] but it's fundamentally always tied
to a specific frame and as such we've always attached it to that frame
using a radiotap vendor namespace.
You can easily implement that in a mac80211 driver since it has support
for that via RX_FLAG_RADIOTAP_VENDOR_DATA and the associated struct
ieee80211_vendor_radiotap that you put into the skb's head.
Why should anything else be needed?
johannes
[1] mostly depending on the bandwidth
next prev parent reply other threads:[~2017-10-23 20:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-23 17:54 A good way to get CSI info to user-space? Ben Greear
2017-10-23 20:30 ` Johannes Berg [this message]
2017-10-23 20:59 ` Ben Greear
2017-10-24 5:54 ` Johannes Berg
2017-10-24 13:36 ` Ben Greear
2017-10-24 13:38 ` Johannes Berg
2017-10-24 13:50 ` Ben Greear
2017-10-24 13:55 ` Johannes Berg
2017-10-24 20:15 ` Ben Greear
2017-10-25 14:30 ` Zefir Kurtisi
2017-10-25 14:43 ` Ben Greear
2017-10-25 15:35 ` Zefir Kurtisi
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=1508790635.2639.24.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.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.