Message ID | 20250307112816.1495-1-peter.ujfalusi@linux.intel.com (mailing list archive) |
---|---|
Headers | show |
Series | ASoC: SOF: Intel: Add support for ACE3+ mic privacy | expand |
On Fri, 07 Mar 2025 13:28:08 +0200, Peter Ujfalusi wrote: > Changes since v1: > - Use type aware condition checks for 'alt' in patch 8 > > Cover letter from v1: > > ACE3 (Panther Lake) introduced support for microphone privacy feature which > can - in hardware - mute incoming audio data based on a state of a physical > switch. > The change in the privacy state is delivered through interface IP blocks > and can only be handled by the link owner. > In Intel platforms Soundwire is for example host owned, so the interrupt > can only be handled by the host. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [1/8] ASoC: SOF: Intel: mtl: Split up dsp_ops setup code commit: 69823334200029767de785d30acf74e4872a11d3 [2/8] ASoC: SOF: Intel: lnl/ptl: Only set dsp_ops which differs from MTL commit: 0d2d276f53ea3ba1686619cde503d9748f58a834 [3/8] ASoC: SOF: Intel: mtl: Stop exporting dsp_ops callback functions commit: 80416226920c21e806f93bd0930d67557f41600f [4/8] ASoC: SOF: Intel: Create ptl.c as placeholder for Panther Lake features commit: 8aeb7d2c3fc315e629d252cd601598a5af74bbb0 [5/8] ASoC: SOF: ipc4: Add support for Intel HW managed mic privacy messaging commit: eea84a7f0cdb693c261a7cf84bd4b3d81479c9a6 [6/8] ASoC: SOF: Intel: hda-mlink: Add support for mic privacy in VS SHIM registers commit: 0978e8207b61ac6d51280e5d28ccfff75d653363 [7/8] ASoC: SOF: hda/shim: Add callbacks to handle mic privacy change for sdw commit: a0db661e7d8e084e9cf3b9cdca7c6e4e66f2e849 [8/8] ASoC: SOF: Intel: ptl: Add support for mic privacy commit: 4a43c3241ec3465a501825ecaf051e5a1d85a60b 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