- Alsa-devel - mailman.alsa-project.org

Re: [PATCH v1] ALSA: hda/tas2781: Add bus name in device name check
by Takashi Iwai 03 Jul '25

03 Jul '25

On Thu, 03 Jul 2025 02:06:08 +0200, Baojun Xu wrote: > > Device name start from bus name, as we use strstarts() > to do compare, need add it for TXNW2781 device. > > Signed-off-by: Baojun Xu <baojun.xu(a)ti.com> Could you give the proper Fixes tag if it's a fix of the previous changes? thanks, Takashi > --- > sound/pci/hda/tas2781_hda_i2c.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/sound/pci/hda/tas2781_hda_i2c.c b/sound/pci/hda/tas2781_hda_i2c.c > index b9cdbca95..530c2266a 100644 > --- a/sound/pci/hda/tas2781_hda_i2c.c > +++ b/sound/pci/hda/tas2781_hda_i2c.c > @@ -588,7 +588,7 @@ static int tas2781_hda_i2c_probe(struct i2c_client *clt) > hda_priv->save_calibration = tas2781_save_calibration; > tas_hda->priv->global_addr = TAS2781_GLOBAL_ADDR; > } else if (strstarts(dev_name(&clt->dev), > - "TXNW2781:00-tas2781-hda.0")) { > + "i2c-TXNW2781:00-tas2781-hda.0")) { > device_name = "TXNW2781"; > hda_priv->save_calibration = tas2781_save_calibration; > tas_hda->priv->global_addr = TAS2781_GLOBAL_ADDR; > -- > 2.43.0 >

1 0

[PATCH 0/3] Add legacy driver support for ACP7.2 based
by Venkata Prasad Potturu 02 Jul '25

02 Jul '25

This patch series is to add I2S and PDM support for ACP7.2 based platforms. Venkata Prasad Potturu (3): ASoC: amd: acp: Add legacy driver support acp7.2 based platforms ASoC: amd: acp: Enable I2S support for acp7.2 based platforms ASoC: amd: acp: Enable acp7.2 platform based DMIC support in machine driver sound/soc/amd/acp/acp-i2s.c | 3 +++ sound/soc/amd/acp/acp-legacy-common.c | 2 ++ sound/soc/amd/acp/acp-mach-common.c | 1 + sound/soc/amd/acp/acp-pci.c | 1 + sound/soc/amd/acp/acp-platform.c | 2 ++ sound/soc/amd/acp/acp70.c | 1 + sound/soc/amd/acp/acp_common.h | 1 + 7 files changed, 11 insertions(+) -- 2.43.0

2 4

New Card: ESI Juli@ eX
by GitHub issues - opened 01 Jul '25

01 Jul '25

alsa-project/alsa-lib issue #462 was opened from Carlisle96: I am not sure where to ask or how to report this: There was a new card released ESI-Audio Juli@ eX https://www.esi-audio.com/products/juliaex/ I am wondering if this is supported or planned to be supported. It is not yet listed here: https://www.alsa-project.org/wiki/Matrix:Vendor-ESI Issue URL : https://github.com/alsa-project/alsa-lib/issues/462 Repository URL: https://github.com/alsa-project/alsa-lib

1 0

Request for help: Outputting audio as an I2S stream
by Steve Broshar 01 Jul '25

01 Jul '25

Summary: My goal is to output audio to an ADAU1467 via I2S on Linux 6.6. I tried and then abandoned using a custom, device-specific driver. Now trying to use built-in simple-sound-card. But, driver does not initialize (probe). Don't know how to debug/fix the issue. I've been working with chapgpt extensively since I have found no other source of information on how to setup linux to output an I2S audio stream. In fact, I posted a question to a linux maillist about an issue a couple weeks ago and the reply from Lars Clausen showed output from chatgpt. In the old days folks would joke about googling something for someone. Today, I guess we can do the same WRT chatgpt. But, that question was about updating a driver. Chatgpt tells me that I shouldn't need a device-specific driver since the device is configured and controlled elsewhere. I just need to pump an audio stream into it. So, I started over with my solution; no longer working on a custom driver. Apparently, I can use the simple-sound-card and a dummy codec. But, it does not work. Maybe chatgpt is wrong and I need a device-specific driver. Or maybe my setup is wrong. I have worked with chatgpt to resolve my issues, but have hit a wall. Hoping to get help from humans now. 😊 The boot-time log (attached) shows nothing about my audio setup until the last line: platform sound-i2s: deferred probe pending I think that ‘deferred probe’ means that an initial probe failed. How can I tell what failed? What prevented it from succeeding? Would be nice if the driver told me what failed. But, there’s no error message, just an info msg that probe is pending. Here's the device tree setup that I added (based on input from chatgpt): / { // Compton audio output can be accomplished via a built-in driver -- simple-audio-card sound_i2s: sound-i2s { // specify the built-in simple sound card compatible = "simple-audio-card"; // seems to be a descriptive name that shows in userland; i.e. via 'aplay -l' simple-audio-card,name = "imx8mn-adauslave"; // might specify I2S (as opposed to descriptive text) simple-audio-card,format = "i2s"; // defines CPU as master for bit-clock simple-audio-card,bitclock-master = <&sound_i2s_cpu>; // defines CPU as master for frame-clock simple-audio-card,frame-master = <&sound_i2s_cpu>; sound_i2s_cpu: simple-audio-card,cpu { sound-dai = <&sai3>; dai-tdm-slot-num = <2>; /* stereo */ dai-tdm-slot-width = <32>; /* bits per slot */ }; simple-audio-card,codec { sound-dai = <&dummy_codec>; }; }; // Compton audio output does not require a device-specific codec; the built-in, dummy driver is sufficient dummy_codec: dummy-codec { compatible = "linux,snd-soc-dummy"; #sound-dai-cells = <0>; }; Here's the device tree config that comes with the NXP IMX8M build for nano: pinctrl_sai3: sai3grp { fsl,pins = < MX8MN_IOMUXC_SAI3_TXFS_SAI3_TX_SYNC 0xd6 MX8MN_IOMUXC_SAI3_TXC_SAI3_TX_BCLK 0xd6 MX8MN_IOMUXC_SAI3_MCLK_SAI3_MCLK 0xd6 MX8MN_IOMUXC_SAI3_TXD_SAI3_TX_DATA0 0xd6 >; }; sai3: sai@30030000 { compatible = "fsl,imx8mn-sai", "fsl,imx8mq-sai"; reg = <0x30030000 0x10000>; #sound-dai-cells = <0>; interrupts = <GIC_SPI 50 IRQ_TYPE_LEVEL_HIGH>; clocks = <&clk IMX8MN_CLK_SAI3_IPG>, <&clk IMX8MN_CLK_DUMMY>, <&clk IMX8MN_CLK_SAI3_ROOT>, <&clk IMX8MN_CLK_DUMMY>, <&clk IMX8MN_CLK_DUMMY>; clock-names = "bus", "mclk0", "mclk1", "mclk2", "mclk3"; dmas = <&sdma2 4 2 0>, <&sdma2 5 2 0>; dma-names = "rx", "tx"; status = "disabled"; }; &sai3 { #sound-dai-cells = <0>; pinctrl-names = "default"; pinctrl-0 = <&pinctrl_sai3>; assigned-clocks = <&clk IMX8MN_CLK_SAI3>; assigned-clock-parents = <&clk IMX8MN_AUDIO_PLL1_OUT>; assigned-clock-rates = <24576000>; fsl,sai-mclk-direction-output; status = "okay"; }; In summary, how do I further debug this? In general, and if you know, how does one output an audio stream as I2S? Steve Broshar Palmer Wireless Medtech

2 1

[PATCH v1] ASoC: Intel: soc-acpi-intel-ptl-match: Add rt721_l0 support
by Ajye Huang 30 Jun '25

30 Jun '25

Patch adds driver data & match table for rt721 multi-function codec on PTL at sdw link0. Signed-off-by: Ajye Huang <ajye_huang(a)compal.corp-partner.google.com> --- .../intel/common/soc-acpi-intel-ptl-match.c | 24 +++++++++++++++++++ 1 file changed, 24 insertions(+) diff --git a/sound/soc/intel/common/soc-acpi-intel-ptl-match.c b/sound/soc/intel/common/soc-acpi-intel-ptl-match.c index eae75f3f0fa4..0257e12e8b6e 100644 --- a/sound/soc/intel/common/soc-acpi-intel-ptl-match.c +++ b/sound/soc/intel/common/soc-acpi-intel-ptl-match.c @@ -330,6 +330,15 @@ static const struct snd_soc_acpi_adr_device rt1320_3_group1_adr[] = { } }; +static const struct snd_soc_acpi_adr_device rt721_0_single_adr[] = { + { + .adr = 0x000030025d072101ull, + .num_endpoints = ARRAY_SIZE(rt_mf_endpoints), + .endpoints = rt_mf_endpoints, + .name_prefix = "rt721" + } +}; + static const struct snd_soc_acpi_adr_device rt721_3_single_adr[] = { { .adr = 0x000330025d072101ull, @@ -339,6 +348,15 @@ static const struct snd_soc_acpi_adr_device rt721_3_single_adr[] = { } }; +static const struct snd_soc_acpi_link_adr ptl_rt721_l0[] = { + { + .mask = BIT(0), + .num_adr = ARRAY_SIZE(rt721_0_single_adr), + .adr_d = rt721_0_single_adr, + }, + {} +}; + static const struct snd_soc_acpi_link_adr ptl_rt721_l3[] = { { .mask = BIT(3), @@ -664,6 +682,12 @@ struct snd_soc_acpi_mach snd_soc_acpi_intel_ptl_sdw_machines[] = { .sof_tplg_filename = "sof-ptl-rt712-l3-rt1320-l3.tplg", .get_function_tplg_files = sof_sdw_get_tplg_files, }, + { + .link_mask = BIT(0), + .links = ptl_rt721_l0, + .drv_name = "sof_sdw", + .sof_tplg_filename = "sof-ptl-rt721.tplg", + }, { .link_mask = BIT(3), .links = ptl_rt721_l3, -- 2.25.1

1 0

ucm2: Qualcomm: Add Dell Latitude 7455 / Inspiron 14 Plus 7441 support
by GitHub pull_request - edited 29 Jun '25

29 Jun '25

alsa-project/alsa-ucm-conf pull request #589 was edited from valpackett: (Both SKUs are identical, the codename is Thena) This configuration is: - 4 speakers - 2 DMICs - headset with mic - DisplayPort (not yet) --- audioreach: https://github.com/linux-msm/audioreach-topology/pull/25 cc @0xB0D @alexVinarskis Request URL : https://github.com/alsa-project/alsa-ucm-conf/pull/589 Patch URL : https://github.com/alsa-project/alsa-ucm-conf/pull/589.patch Repository URL: https://github.com/alsa-project/alsa-ucm-conf

1 0

ucm2: Qualcomm: Add Dell Latitude 7455 / Inspiron 14 Plus 7441 support
by GitHub pull_request - opened 29 Jun '25

29 Jun '25

alsa-project/alsa-ucm-conf pull request #589 was opened from valpackett: (Both SKUs are identical, the codename is Thena) This configuration is: - 4 speakers - 2 DMICs - headset with mic - DisplayPort (not yet) --- cc @0xB0D @alexVinarskis Request URL : https://github.com/alsa-project/alsa-ucm-conf/pull/589 Patch URL : https://github.com/alsa-project/alsa-ucm-conf/pull/589.patch Repository URL: https://github.com/alsa-project/alsa-ucm-conf

1 0

Focusrite Scarlett 18i20 Gen 1: UCM configuration defines incorrect capture channel count
by GitHub issues - opened 29 Jun '25

29 Jun '25

alsa-project/alsa-ucm-conf issue #588 was opened from mkuhl: ## Summary The ALSA UCM configuration for Focusrite Scarlett 18i20 incorrectly defines 20 capture channels (`Define.DirectCaptureChannels 20`), but the 1st generation hardware only supports 18 channels. This causes the device to fail initialization with UCM profile errors. ## Device Information - **Device**: Focusrite Scarlett 18i20 (1st Generation) - **USB ID**: 1235:800c - **USB Name**: Focusrite Scarlett 18i20 USB - **Driver**: snd_usb_audio ## Channel Configuration (Gen 1) - 8 analog inputs - 8 ADAT inputs - 2 S/PDIF inputs - **Total**: 18 input channels (not 20) ## Error Message ``` spa.alsa: Error in ALSA UCM profile for _ucm0007.hw:USB,0 (HiFi: Direct 2: source): CaptureChannels=20 > avail 18 spa.alsa: Errors in ALSA UCM profile for card Scarlett 18i20 ``` ## Affected Files The channel definition is in the main configuration file: `/usr/share/alsa/ucm2/USB-Audio/Focusrite/Scarlett-18i20.conf` Current (incorrect): ``` Define.DirectCaptureChannels 20 ``` Should be: ``` Define.DirectCaptureChannels 18 ``` This file then includes `Scarlett-18i20-HiFi.conf` which uses the defined value. ## System Information - **Distribution**: Fedora 42 / Aurora-dx - **Kernel**: 6.15.3-200.fc42.x86_64 - **PipeWire**: 1.4.5-1.fc42 - **WirePlumber**: 0.5.8-1.fc42 - **ALSA UCM**: 1.2.14-2.fc42 - **ALSA lib**: 1.2.14-2.fc42 ## Steps to Reproduce 1. Connect Focusrite Scarlett 18i20 Gen 1 (USB ID 1235:800c) 2. Start PipeWire/WirePlumber 3. Check device status: `wpctl status | grep Scarlett` 4. Device shows "[ALSA UCM error]" 5. Journal shows channel count mismatch error ## Workaround Users can create a local override: ```bash mkdir -p ~/.local/share/alsa/ucm2/USB-Audio/Focusrite/ cp /usr/share/alsa/ucm2/USB-Audio/Focusrite/Scarlett-18i20.conf \ ~/.local/share/alsa/ucm2/USB-Audio/Focusrite/ cp /usr/share/alsa/ucm2/USB-Audio/Focusrite/Scarlett-18i20-HiFi.conf \ ~/.local/share/alsa/ucm2/USB-Audio/Focusrite/ sed -i 's/Define.DirectCaptureChannels 20/Define.DirectCaptureChannels 18/g' \ ~/.local/share/alsa/ucm2/USB-Audio/Focusrite/Scarlett-18i20.conf ``` ## Root Cause Analysis The UCM configuration appears to be written for newer Scarlett 18i20 generations (2nd/3rd/4th Gen) which may have 20 channels due to additional loopback channels. The configuration includes generation detection logic but doesn't properly identify USB ID 1235:800c as a 1st Gen device, causing it to use the default 20-channel configuration. ## Proposed Solution The UCM configuration should detect Gen 1 devices and set the appropriate channel count: 1. Add detection for USB ID 1235:800c as Gen 1 2. Set `DirectCaptureChannels` to 18 for Gen 1 devices 3. Keep 20 channels for newer generations if applicable ## Impact - Device fails to initialize properly - Users cannot use the audio interface without manual workarounds - Affects all Linux distributions using this UCM configuration ## Additional Information - This is a regression - older ALSA versions worked correctly - The issue affects PipeWire/WirePlumber but not JACK when using Pro Audio profile (which bypasses UCM) - Other Gen 1 Scarlett devices (6i6, 8i8) may have similar issues ## References - Device specifications: https://support.focusrite.com/hc/en-gb/articles/206849839-Scarlett-1st-Gen-… Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/588 Repository URL: https://github.com/alsa-project/alsa-ucm-conf

1 0

tascam us 322 / 366
by GitHub issues - edited 29 Jun '25

29 Jun '25

alsa-project/alsa-firmware issue #12 was edited from riramau: Can someone add support for tascam 322 / 366 ? Issue URL : https://github.com/alsa-project/alsa-firmware/issues/12 Repository URL: https://github.com/alsa-project/alsa-firmware

1 0

tascam us 322 / 366
by GitHub issues - opened 29 Jun '25

29 Jun '25

alsa-project/alsa-firmware issue #12 was opened from riramau: Can someone add support of tascam 322 / 366 ? Issue URL : https://github.com/alsa-project/alsa-firmware/issues/12 Repository URL: https://github.com/alsa-project/alsa-firmware

1 0