All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Arend van Spriel <arend.vanspriel@broadcom.com>,
	Lior David <liord@codeaurora.org>, Luca Coelho <luca@coelho.fi>
Cc: Maya Erez <merez@codeaurora.org>,
	Jouni Malinen <jouni@qca.qualcomm.com>,
	linux-wireless@vger.kernel.org
Subject: Re: nl80211 fine timing measurement support
Date: Tue, 04 Oct 2016 11:25:42 +0200	[thread overview]
Message-ID: <1475573142.5324.41.camel@sipsolutions.net> (raw)
In-Reply-To: <6b1f015b-2796-9821-25c6-d4d5070939c9@broadcom.com> (sfid-20161001_115652_871760_B91DD921)


> If raw results are mainly used for analysis algorithms how about
> providing raw measurement data through debugfs. May even consider
> adding rtt calculation in cfg80211/mac80211 for drivers that choose
> to provide raw measurement data and still only report final RTT in
> nl80211 api.
> 

I think the "analysis algorithms" in this case are what actually gives
you the distance value.

However, I don't think we should accept that everybody wants to run
their proprietary algorithms on top and expose only the values needed
for those. That makes the drivers only usable with additional
proprietary software, which may even be incompatible with the GPL.

If the algorithms are in the device, then we can expose the final
results, and that's most useful for applications in the API.

If they're not, then we need to expose something that can be used
without additional proprietary and device-specific algorithms.

If those algorithms cannot be run in the device, then we should put
them into the driver instead.

johannes

  reply	other threads:[~2016-10-04  9:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-19 17:31 nl80211 fine timing measurement support Lior David
2016-09-19 18:42 ` Arend Van Spriel
2016-09-19 19:41   ` Johannes Berg
2016-09-20  6:39   ` Luca Coelho
2016-09-20 20:57     ` Lior David
2016-10-01  9:56       ` Arend van Spriel
2016-10-04  9:25         ` Johannes Berg [this message]
2016-10-06  8:41           ` Lior David

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=1475573142.5324.41.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=arend.vanspriel@broadcom.com \
    --cc=jouni@qca.qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=liord@codeaurora.org \
    --cc=luca@coelho.fi \
    --cc=merez@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.