On Thu, 2 Sep 2021 14:53:28 +0300, Peter Ujfalusi wrote: > If the value/data associated with a control changes in SOF it will send a > notification (SOF_IPC_GLB_COMP_MSG with SOF_IPC_COMP_GET_VALUE/DATA). > > We have support for binary volatile control type, but we might have > features where enum/switch/volume changes. Re-implementing everything as > volatile as well would be not much of a gain for several reasons: > - volatile controls would do an IPC all the time, regardless if there is a > need or not. > - We still don't have notification which forces userspace to continuously > poll. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [1/1] ASoC: SOF: Handle control change notification from firmware commit: 756bbe4205bc63a84ab032a1b76970afe55e2d9d All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted. You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed. If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced. Please add any relevant lists and maintainers to the CCs when replying to this mail. Thanks, Mark
