Searched hist:"14055 b5a3a23204c4702ae5d3f2a819ee081ce33" (Results 1 – 2 of 2) sorted by relevance
/linux/include/linux/firmware/cirrus/ |
H A D | cs_dsp.h | diff 14055b5a3a23204c4702ae5d3f2a819ee081ce33 Wed Nov 17 14:22:54 CET 2021 Charles Keepax <ckeepax@opensource.cirrus.com> firmware: cs_dsp: Add pre_run callback
The code already has a post_run callback, add a matching pre_run callback to the client_ops that is called before execution is started. This callback provides a convenient place for the client code to set DSP controls or hardware that requires configuration before the DSP core actually starts execution. Note that placing this callback before cs_dsp_coeff_sync_controls is important to ensure that any control values are then correctly synced out to the chip.
Co-authored-by: Simon Trimmer <simont@opensource.cirrus.com> Signed-off-by: Simon Trimmer <simont@opensource.cirrus.com> Signed-off-by: Charles Keepax <ckeepax@opensource.cirrus.com> Link: https://lore.kernel.org/r/20211117132300.1290-4-ckeepax@opensource.cirrus.com Signed-off-by: Mark Brown <broonie@kernel.org>
|
/linux/drivers/firmware/cirrus/ |
H A D | cs_dsp.c | diff 14055b5a3a23204c4702ae5d3f2a819ee081ce33 Wed Nov 17 14:22:54 CET 2021 Charles Keepax <ckeepax@opensource.cirrus.com> firmware: cs_dsp: Add pre_run callback
The code already has a post_run callback, add a matching pre_run callback to the client_ops that is called before execution is started. This callback provides a convenient place for the client code to set DSP controls or hardware that requires configuration before the DSP core actually starts execution. Note that placing this callback before cs_dsp_coeff_sync_controls is important to ensure that any control values are then correctly synced out to the chip.
Co-authored-by: Simon Trimmer <simont@opensource.cirrus.com> Signed-off-by: Simon Trimmer <simont@opensource.cirrus.com> Signed-off-by: Charles Keepax <ckeepax@opensource.cirrus.com> Link: https://lore.kernel.org/r/20211117132300.1290-4-ckeepax@opensource.cirrus.com Signed-off-by: Mark Brown <broonie@kernel.org>
|