From: Kalle Valo <kvalo@codeaurora.org>
To: "Mishol\, Guy" <guym@ti.com>
Cc: "Pedersen\, Thomas" <twp@qca.qualcomm.com>,
"linux-wireless\@vger.kernel.org"
<linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] wlcore: mesh: add zone time sync support
Date: Mon, 22 Aug 2016 18:56:01 +0300 [thread overview]
Message-ID: <87k2f8vlv2.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <97207D90F0289D498537011312FCAD1138F55E66@DFRE01.ent.ti.com> (Guy Mishol's message of "Sun, 21 Aug 2016 10:13:22 +0000")
"Mishol, Guy" <guym@ti.com> writes:
> Kalle/Thomas,
> Thanks for your feedback.
Please don't top most, it makes using patchwork difficult and is
annoying to the readers.
> This time sync support is different from the one that mac80211
> maintains with mesh peers. This time sync is mostly used by upper
> layers for several applications (like audio). In this case we allow
> the user to configure for each zone who will be the synchronizer. You
> can refer to the following Application Report (chapter 6) for more
> information: http://www.ti.com/lit/an/swaa166/swaa166.pdf
I didn't fully understand what this does, but debugfs doesn't sound (no
pun intended) like a suitable interface for something like this. nl80211
is more likely candidate.
--
Kalle Valo
next prev parent reply other threads:[~2016-08-22 16:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 8:57 [PATCH] wlcore: mesh: add zone time sync support Guy Mishol
2016-08-18 16:42 ` Pedersen, Thomas
2016-08-19 9:57 ` Kalle Valo
2016-08-21 10:13 ` Mishol, Guy
2016-08-22 15:56 ` Kalle Valo [this message]
2016-08-23 9:12 ` Mishol, Guy
2016-08-25 18:50 ` Pedersen, Thomas
2016-08-28 7:34 ` Mishol, Guy
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=87k2f8vlv2.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=guym@ti.com \
--cc=linux-wireless@vger.kernel.org \
--cc=twp@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).