Skip to content

Commit

Permalink
audio: module-interface: better explain .trigger method
Browse files Browse the repository at this point in the history
struct module_interface::trigger() is called from both hot and cold
contexts, therefore it usually shouldn't be marked as __cold.

Signed-off-by: Guennadi Liakhovetski <guennadi.liakhovetski@linux.intel.com>
  • Loading branch information
lyakh committed Mar 4, 2025
1 parent 9a886fd commit 4db3875
Showing 1 changed file with 3 additions and 1 deletion.
4 changes: 3 additions & 1 deletion src/include/module/module/interface.h
Original file line number Diff line number Diff line change
Expand Up @@ -239,7 +239,9 @@ struct module_interface {

/**
* (optional) Module specific trigger procedure, called when modules are triggered. Usually
* can be __cold
* shouldn't be __cold. If a module implements this method, even if it only handles
* commands, running in non-LL context, it will still be called from the high priority
* LL context, which will cause a short jump to DRAM to check for supported commands.
*/
int (*trigger)(struct processing_module *mod, int cmd);

Expand Down

0 comments on commit 4db3875

Please sign in to comment.