<feed xmlns='http://www.w3.org/2005/Atom'>
<title>wireguard-linux/sound, branch stable</title>
<subtitle>WireGuard for the Linux kernel</subtitle>
<id>https://git.zx2c4.com/wireguard-linux/atom/sound?h=stable</id>
<link rel='self' href='https://git.zx2c4.com/wireguard-linux/atom/sound?h=stable'/>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/'/>
<updated>2025-10-30T12:08:08Z</updated>
<entry>
<title>Merge tag 'asoc-fix-v6.18-rc2' of https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound into for-linus</title>
<updated>2025-10-30T12:08:08Z</updated>
<author>
<name>Takashi Iwai</name>
<email>tiwai@suse.de</email>
</author>
<published>2025-10-30T12:08:08Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/commit/?id=390db60f8e2bd21fae544917eb3a8618265c058c'/>
<id>urn:sha1:390db60f8e2bd21fae544917eb3a8618265c058c</id>
<content type='text'>
ASoC: Fixes for v6.18

A bigger batch of fixes than I'd like, things built up due to holidays
and some last minute issues which caused me to hold off on sending a pul
request.  None of these are super remarkable, and there's a few new
device IDs in here too including a relatively big block of AMD devices.

The Cirrus Logic CS530x support subject line is actually a fix that was
on the start of that series and got pulled in here, I forgot to fix the
subject up when merging.
</content>
</entry>
<entry>
<title>ALSA: hda/realtek: Enable mic on Vaio RPL</title>
<updated>2025-10-30T06:26:47Z</updated>
<author>
<name>Edson Juliano Drosdeck</name>
<email>edson.drosdeck@gmail.com</email>
</author>
<published>2025-10-29T18:11:52Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/commit/?id=4f4c654f5a0f6560b938a5ab05ec5940aa6c1c29'/>
<id>urn:sha1:4f4c654f5a0f6560b938a5ab05ec5940aa6c1c29</id>
<content type='text'>
Vaio RPL is equipped with ACL256, and needs a
fix to make the internal mic and headphone mic to work.
Also must to limits the internal microphone boost.

Signed-off-by: Edson Juliano Drosdeck &lt;edson.drosdeck@gmail.com&gt;
Link: https://patch.msgid.link/20251029181152.389302-1-edson.drosdeck@gmail.com
Signed-off-by: Takashi Iwai &lt;tiwai@suse.de&gt;
</content>
</entry>
<entry>
<title>ASoC: renesas: rz-ssi: Use proper dma_buffer_pos after resume</title>
<updated>2025-10-29T14:54:46Z</updated>
<author>
<name>Claudiu Beznea</name>
<email>claudiu.beznea.uj@bp.renesas.com</email>
</author>
<published>2025-10-29T14:11:34Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/commit/?id=22897e568646de5907d4981eae6cc895be2978d1'/>
<id>urn:sha1:22897e568646de5907d4981eae6cc895be2978d1</id>
<content type='text'>
When the driver supports DMA, it enqueues four DMA descriptors per
substream before the substream is started. New descriptors are enqueued in
the DMA completion callback, and each time a new descriptor is queued, the
dma_buffer_pos is incremented.

During suspend, the DMA transactions are terminated. There might be cases
where the four extra enqueued DMA descriptors are not completed and are
instead canceled on suspend. However, the cancel operation does not take
into account that the dma_buffer_pos was already incremented.

Previously, the suspend code reinitialized dma_buffer_pos to zero, but this
is not always correct.

To avoid losing any audio periods during suspend/resume and to prevent
clip sound, save the completed DMA buffer position in the DMA callback and
reinitialize dma_buffer_pos on resume.

Cc: stable@vger.kernel.org
Fixes: 1fc778f7c833a ("ASoC: renesas: rz-ssi: Add suspend to RAM support")
Signed-off-by: Claudiu Beznea &lt;claudiu.beznea.uj@bp.renesas.com&gt;
Link: https://patch.msgid.link/20251029141134.2556926-3-claudiu.beznea.uj@bp.renesas.com
Signed-off-by: Mark Brown &lt;broonie@kernel.org&gt;
</content>
</entry>
<entry>
<title>ASoC: soc_sdw_utils: remove cs42l43 component_name</title>
<updated>2025-10-28T10:22:13Z</updated>
<author>
<name>Bard Liao</name>
<email>yung-chuan.liao@linux.intel.com</email>
</author>
<published>2025-10-27T14:00:12Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/commit/?id=45f5c9eec43a9bf448f46562f146810831916cc9'/>
<id>urn:sha1:45f5c9eec43a9bf448f46562f146810831916cc9</id>
<content type='text'>
"spk:cs42l43-spk" component string will be added conditionally by
asoc_sdw_cs42l43_spk_rtd_init(). We should not add "spk:cs42l43"
unconditionally.

Fixes: c61da55412a0 ("ASoC: sdw_utils: Add missed component_name strings for speaker amps")
Signed-off-by: Bard Liao &lt;yung-chuan.liao@linux.intel.com&gt;
Reviewed-by: Péter Ujfalusi &lt;peter.ujfalusi@linux.intel.com&gt;
Reviewed-by: Charles Keepax &lt;ckeepax@opensource.cirrus.com&gt;
Link: https://patch.msgid.link/20251027140012.966306-1-yung-chuan.liao@linux.intel.com
Signed-off-by: Mark Brown &lt;broonie@kernel.org&gt;
</content>
</entry>
<entry>
<title>ASoC: fsl_sai: Fix sync error in consumer mode</title>
<updated>2025-10-28T10:22:12Z</updated>
<author>
<name>Maarten Zanders</name>
<email>maarten@zanders.be</email>
</author>
<published>2025-10-24T13:57:15Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/commit/?id=b2dd1d0d322dce5f331961c927e775b84014d5ab'/>
<id>urn:sha1:b2dd1d0d322dce5f331961c927e775b84014d5ab</id>
<content type='text'>
When configured for default synchronisation (Rx syncs to Tx) and the
SAI operates in consumer mode (clocks provided externally to Tx), a
synchronisation error occurs on Tx on the first attempt after device
initialisation when the playback stream is started while a capture
stream is already active. This results in channel shift/swap on the
playback stream.
Subsequent streams (ie after that first failing one) always work
correctly, no matter the order, with or without the other stream active.

This issue was observed (and fix tested) on an i.MX6UL board connected
to an ADAU1761 codec, where the codec provides both frame and bit clock
(connected to TX pins).

To fix this, always initialize the 'other' xCR4 and xCR5 registers when
we're starting a stream which is synced to the opposite one, irregardless
of the producer/consumer status.

Fixes: 51659ca069ce ("ASoC: fsl-sai: set xCR4/xCR5/xMR for SAI master mode")

Signed-off-by: Maarten Zanders &lt;maarten@zanders.be&gt;
Reviewed-by: Shengjiu Wang &lt;shengjiu.wang@gmail.com&gt;
Link: https://patch.msgid.link/20251024135716.584265-1-maarten@zanders.be
Signed-off-by: Mark Brown &lt;broonie@kernel.org&gt;
</content>
</entry>
<entry>
<title>ASoC: Fix build for sdw_utils</title>
<updated>2025-10-28T10:21:27Z</updated>
<author>
<name>Mark Brown</name>
<email>broonie@kernel.org</email>
</author>
<published>2025-10-28T10:20:30Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/commit/?id=c8b8804760eb0c4c0c7c2b500380ab3fa9f92b5a'/>
<id>urn:sha1:c8b8804760eb0c4c0c7c2b500380ab3fa9f92b5a</id>
<content type='text'>
Revert 3293d3d7b0 ("ASoC: sdw_utils: add name_prefix for rt1321 part
id") due to dependencies on -next which for some reason don't show up
in my builds.

Signed-off-by: Mark Brown &lt;broonie@kernel.org&gt;
</content>
</entry>
<entry>
<title>ALSA: hda/realtek: Fix mute led for HP Victus 15-fa1xxx (MB 8C2D)</title>
<updated>2025-10-27T14:13:29Z</updated>
<author>
<name>Eren Demir</name>
<email>eren.demir2479090@gmail.com</email>
</author>
<published>2025-10-27T10:58:10Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/commit/?id=28935ee5e4789ad86c08ba9f2426edd6203d13fa'/>
<id>urn:sha1:28935ee5e4789ad86c08ba9f2426edd6203d13fa</id>
<content type='text'>
The quirk for Victus 15-fa1xxx wasn't working on Victus 15-fa1031nt due to a different board id. This patch enables the existing quirk for the board id 8BC8.

Tested on HP Victus 15-fa1031nt (MB 8C2D). The LED behaviour works as intended.

Signed-off-by: Eren Demir &lt;eren.demir2479090@gmail.com&gt;
Link: https://patch.msgid.link/20251027110208.6481-1-eren.demir2479090@gmail.com
Signed-off-by: Takashi Iwai &lt;tiwai@suse.de&gt;
</content>
</entry>
<entry>
<title>ASoC: rt721: fix prepare clock stop failed</title>
<updated>2025-10-27T12:17:05Z</updated>
<author>
<name>Shuming Fan</name>
<email>shumingf@realtek.com</email>
</author>
<published>2025-10-27T10:33:33Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/commit/?id=d914ec6f07548f7c13a231a4f526e043e736e82e'/>
<id>urn:sha1:d914ec6f07548f7c13a231a4f526e043e736e82e</id>
<content type='text'>
This patch adds settings to prevent the 'prepare clock stop failed' error.

Signed-off-by: Shuming Fan &lt;shumingf@realtek.com&gt;
Link: https://patch.msgid.link/20251027103333.38353-1-shumingf@realtek.com
Signed-off-by: Mark Brown &lt;broonie@kernel.org&gt;
</content>
</entry>
<entry>
<title>ALSA: usb-audio: don't log messages meant for 1810c when initializing 1824c</title>
<updated>2025-10-27T08:59:18Z</updated>
<author>
<name>Roy Vegard Ovesen</name>
<email>roy.vegard.ovesen@gmail.com</email>
</author>
<published>2025-10-20T20:15:08Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/commit/?id=75cdae446ddffe0a6a991bbb146dee51d9d4c865'/>
<id>urn:sha1:75cdae446ddffe0a6a991bbb146dee51d9d4c865</id>
<content type='text'>
The log messages for the PreSonus STUDIO 1810c about
device_setup are not applicable to the 1824c, and should
not be logged when 1824c initializes.

Refactor from if statement to switch statement as there
might be more STUDIO series devices added later.

Fixes: 080564558eb1 ("ALSA: usb-audio: enable support for Presonus Studio 1824c within 1810c file")
Signed-off-by: Roy Vegard Ovesen &lt;roy.vegard.ovesen@gmail.com&gt;
Link: https://patch.msgid.link/aPaYTP7ceuABf8c7@ark
Signed-off-by: Takashi Iwai &lt;tiwai@suse.de&gt;
</content>
</entry>
<entry>
<title>ASoC: fsl: correct the bit order issue for DSD</title>
<updated>2025-10-24T10:36:32Z</updated>
<author>
<name>Mark Brown</name>
<email>broonie@kernel.org</email>
</author>
<published>2025-10-24T10:36:32Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/commit/?id=ad68c0536cfc28c161593ca4c896a6e74435394b'/>
<id>urn:sha1:ad68c0536cfc28c161593ca4c896a6e74435394b</id>
<content type='text'>
Merge series from Shengjiu Wang &lt;shengjiu.wang@nxp.com&gt;:

The DSD little endian format requires the msb first, the previous
understanding is not correct. The issue is found by testing with
pipewire.
</content>
</entry>
</feed>
