Repository navigation
keyword detection: explain formula for keyphrase buffer size - #182
Conversation
| Write Pointer (WP) is used to indicate where data coming from microphones is | ||
| written to a keyphrase buffer. The keyphrase buffer is organized as | ||
| a cyclic buffer and WP moves as long as data is coming from mics at | ||
| a regular rate. Read pointer (RP) indicates from which offset in teh buffer |
| a regular rate. Read pointer (RP) indicates from which offset in teh buffer | ||
| data is fetched to host. To start burst transmission RP is set to WP | ||
| position. RP moves faster then WP as draining is executed as a background | ||
| task until RP reaches again WP that moves a a regular (slower) rate. This |
There was a problem hiding this comment.
Also, here we claim that we start draining from WP (write pointer) which is not true - in fact we calculate read position base on host client algorithm / topology param called "history depth".
There was a problem hiding this comment.
@lbetlej @lgirdwood Please let me know if this comment by @mrajwa has been resolved so I can merge this PR. [...in fact we calculate read position base on host client algorithm / topology param called "history depth"]
Thanks.
There was a problem hiding this comment.
@lgirdwood there is nothing more I can say/do in regards to this PR. We have to wait for an update from @lbetlej. He is on sick leave now so let's give him few days until his well.
There was a problem hiding this comment.
@mrajwa Thanks for your update. In the interest of time, I am going to merge PRs 182-183 and also add my own edits. I will make a note of @mrajwa's comments. @lbetlej can update the new page when he returns. Thanks, all.
UPDATE: This branch has conflicts; I suspect they are from PR #183 so I am going to hold off on editing kd-integration.rst until after @lbetlej returns.
There was a problem hiding this comment.
@deb-intel I've rebased and updated the PR to address all findings listed in the conversation. Could you wait for review approval from @mrajwa before you start proof reading ?
lbetlej
changed the title
lbetlej
changed the title
| 3. L3 is a time required to send already buffered data to host. Typically | ||
| Write Pointer (WP) is used to indicate where data coming from microphones is | ||
| written to a keyphrase buffer. The keyphrase buffer is organized as | ||
| a cyclic buffer and WP move if data is coming from mics at |
|
Functional wise its fine for me now. |
An explanation of various types of latencies that determine minimum size of a keyphrase buffer is added. It includes information about differences in movement between write and read pointers to the buffer. Signed-off-by: Lech Betlej <lech.betlej@linux.intel.com>
An explanation of various types of latencies that determine minimum size of
a keyphrase buffer is added. It includes information about differences in
movement between write and read pointers to the buffer.
Signed-off-by: Lech Betlej lech.betlej@linux.intel.com