Skip to content

Commit 5ed3840

Browse files
committed
userspace: doc: describe where DP module objects are allocated
Document that the allocation context, pin formats and configuration buffers of DP modules are in the module vregion, and that the IPC user thread adds kernel-created DP components to the component list. Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
1 parent 9291af1 commit 5ed3840

1 file changed

Lines changed: 5 additions & 0 deletions

File tree

‎src/include/sof/userspace/README.md‎

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -196,6 +196,11 @@ Objects in the kernel areas:
196196
(`struct zephyr_ll`), the LL scheduling domain and its Zephyr domain data, the DP scheduler
197197
data, and the LL tasks that kernel threads create at boot together with their task data.
198198

199+
DP modules are created by kernel code, but their allocation context, pin format arrays and
200+
configuration buffers are in the module's own vregion, released with it, and the IPC user
201+
thread adds the component to the component list. So creating a DP module does not allocate
202+
from the LL user heap in kernel code.
203+
199204
The LL timer interrupt and the LL thread setup and teardown use kernel-only copies of the
200205
domain data pointer, the per-core semaphores and the LL threads, not the user-writable domain
201206
data.

0 commit comments

Comments
 (0)