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

USB-Audio: Device or resource busy
by Muni Sekhar 11 Aug '21

11 Aug '21

Hi All, $ cat /proc/asound/cards 0 [USB ]: USB-Audio - Plantronics .Audio 628 USB Plantronics Plantronics .Audio 628 USB at usb-0000:00:14.0-2, full speed I am using a Plantronics USB Audio headset. $ arecord --device hw:0,0 --channels 2 --format S16_LE --rate 44100Hz x.wav arecord: main:722: audio open error: Device or resource busy 'arecord' command always fails the first time after system boot in my system. But subsequent execution of the 'arecord' command runs fine. I've attached the strace log for the "audio open error: Device or resource busy" failure. Is there any fix available for this issue? -- Thanks, Sekhar

1 0

Unable to clone repo from windows or yocto
by GitHub issues - edited 11 Aug '21

11 Aug '21

alsa-project/tinycompress issue #11 was edited from boppana113: Attempted to clone the github repo using the following command: - git clone git://git.alsa-project.org/tinycompress.git I got the following error: ``` $ git clone git://git.alsa-project.org/tinycompress.git Cloning into 'tinycompress'... fatal: unable to connect to git.alsa-project.org: git.alsa-project.org[0: 207.180.221.201]: errno=Unknown error ``` The git clone command appears to timeout Issue URL : https://github.com/alsa-project/tinycompress/issues/11 Repository URL: https://github.com/alsa-project/tinycompress

1 0

Unable to clone repo from windows or yocto
by GitHub issues - opened 11 Aug '21

11 Aug '21

alsa-project/tinycompress issue #11 was opened from boppana113: Attempted to clone the github repo using the following command: - git clone git://git.alsa-project.org/tinycompress.git I got the following error: ``` $ git clone git://git.alsa-project.org/tinycompress.git Cloning into 'tinycompress'... fatal: unable to connect to git.alsa-project.org: git.alsa-project.org[0: 207.180.221.201]: errno=Unknown error ``` Issue URL : https://github.com/alsa-project/tinycompress/issues/11 Repository URL: https://github.com/alsa-project/tinycompress

1 0

Re: CORB reset timeout, Intel 3400 onboard chip
by tom 11 Aug '21

11 Aug '21

On 21/08/10 09:21PM, tom wrote: > On 21/08/10 09:16PM, tom wrote: > > On 21/08/10 06:03PM, Pierre-Louis Bossart wrote: > > > > > > > > > On 8/10/21 5:35 PM, tom wrote: > > > > Hello all, > > > > I am experiencing an issue with my onboard sound card, where I have no sound > > > > output. Please see a copy of my alsa-info.sh for my current > > > > /etc/modprobe.d/*.conf config, located here: > > > > > > > > http://ix.io/3vAV > > > > > > > > I attempted troubleshooting using some config options that I saw listed in > > > > HDAudio.txt. Specifically, I tried model options for "generic". I also tried a > > > > few options for probe_mask, including "1" and "0x100". > > > > > > > > > > > > It seems that no matter which options I put in, I always get a > > > > CORB timeout from desg: > > > > > > > > [ 4.052955] snd_hda_intel 0000:00:1b.0: CORB reset timeout#1, CORBRP = 0 > > > > [ 4.053038] snd_hda_intel 0000:00:1b.0: no codecs initialized > > > > > > > > When I remove my probe_mask options, it first switches to polling mode, then > > > > single_cmd mode, and finally fails to initialize any codecs. I looked at the > > > > hda_intel.c file and saw a section for my onboard sound card (ref line 2515): > > > > > > > > 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High > > > > Definition Audio (rev 05) > > > > > > In the alsa-info.sh log, I can see this > > > [ 3.950319] snd_hda_intel 0000:00:1b.0: codec_mask forced to 0x0 > > > > > > I am not sure how this might happen, this looks like a bad configuration > > > to me? > > > > > > /* check forced option */ > > > if (chip->codec_probe_mask != -1 && > > > (chip->codec_probe_mask & AZX_FORCE_CODEC_MASK)) { > > > azx_bus(chip)->codec_mask = chip->codec_probe_mask & 0xff; > > > dev_info(chip->card->dev, "codec_mask forced to 0x%x\n", > > > (int)azx_bus(chip)->codec_mask); > > > } > > Hello Pierre, My /etc/modprobe.d/alsa-base.conf file looks as follows: options snd_hda_intel probe_mask=0x100 And this was based on a suggestion from "HDAudio.txt" If I comment this line out, I will instead get the following from the command "sudo dmesg | grep -i snd": [ 4.110018] snd_hda_intel 0000:00:1b.0: CORB reset timeout#1, CORBRP = 0 [ 5.114462] snd_hda_intel 0000:00:1b.0: azx_get_response timeout, switching to polling mode: last cmd=0x100f0000 [ 6.124488] snd_hda_intel 0000:00:1b.0: No response from codec, disabling MSI: last cmd=0x100f0000 [ 7.131158] snd_hda_intel 0000:00:1b.0: Codec #1 probe error; disabling it... [ 7.236557] snd_hda_intel 0000:00:1b.0: CORB reset timeout#1, CORBRP = 0 [ 8.244423] snd_hda_intel 0000:00:1b.0: azx_get_respons timeout, switching to single_cmd mode: last cmd=0x100f0000 [ 8.244955] snd_hda_intel 0000:00:1b.0: no codecs initialized I hope this helps!

1 0

[PATCH v2] ASoC: Intel: Fix platform ID matching
by Curtis Malainey 11 Aug '21

11 Aug '21

Sparse warnings triggered truncating the IDs of some platform device tables. Unfortunately some of the IDs in the match tables were missed which breaks audio. The KBL change has been verified to fix audio, the CML change was not tested as it was found through grepping the broken changes and found to match the same situation in anticipation that it should also be fixed. Fixes: 94efd726b947 ("ASoC: Intel: kbl_da7219_max98357a: shrink platform_id below 20 characters") Fixes: 24e46fb811e9 ("ASoC: Intel: bxt_da7219_max98357a: shrink platform_id below 20 characters") Signed-off-by: Curtis Malainey <cujomalainey(a)chromium.org> Tested-by: Matt Davis <mattedavis(a)google.com> --- sound/soc/intel/common/soc-acpi-intel-cml-match.c | 2 +- sound/soc/intel/common/soc-acpi-intel-kbl-match.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/sound/soc/intel/common/soc-acpi-intel-cml-match.c b/sound/soc/intel/common/soc-acpi-intel-cml-match.c index 42ef51c3fb4f..b591c6fd13fd 100644 --- a/sound/soc/intel/common/soc-acpi-intel-cml-match.c +++ b/sound/soc/intel/common/soc-acpi-intel-cml-match.c @@ -75,7 +75,7 @@ struct snd_soc_acpi_mach snd_soc_acpi_intel_cml_machines[] = { }, { .id = "DLGS7219", - .drv_name = "cml_da7219_max98357a", + .drv_name = "cml_da7219_mx98357a", .machine_quirk = snd_soc_acpi_codec_list, .quirk_data = &max98390_spk_codecs, .sof_fw_filename = "sof-cml.ri", diff --git a/sound/soc/intel/common/soc-acpi-intel-kbl-match.c b/sound/soc/intel/common/soc-acpi-intel-kbl-match.c index ba5ff468c265..741bf2f9e081 100644 --- a/sound/soc/intel/common/soc-acpi-intel-kbl-match.c +++ b/sound/soc/intel/common/soc-acpi-intel-kbl-match.c @@ -87,7 +87,7 @@ struct snd_soc_acpi_mach snd_soc_acpi_intel_kbl_machines[] = { }, { .id = "DLGS7219", - .drv_name = "kbl_da7219_max98357a", + .drv_name = "kbl_da7219_mx98357a", .fw_filename = "intel/dsp_fw_kbl.bin", .machine_quirk = snd_soc_acpi_codec_list, .quirk_data = &kbl_7219_98357_codecs, -- 2.32.0.605.g8dce9f2422-goog

5 4

CORB reset timeout, Intel 3400 onboard chip
by tom 11 Aug '21

11 Aug '21

Hello all, I am experiencing an issue with my onboard sound card, where I have no sound output. Please see a copy of my alsa-info.sh for my current /etc/modprobe.d/*.conf config, located here: http://ix.io/3vAV I attempted troubleshooting using some config options that I saw listed in HDAudio.txt. Specifically, I tried model options for "generic". I also tried a few options for probe_mask, including "1" and "0x100". It seems that no matter which options I put in, I always get a CORB timeout from desg: [ 4.052955] snd_hda_intel 0000:00:1b.0: CORB reset timeout#1, CORBRP = 0 [ 4.053038] snd_hda_intel 0000:00:1b.0: no codecs initialized When I remove my probe_mask options, it first switches to polling mode, then single_cmd mode, and finally fails to initialize any codecs. I looked at the hda_intel.c file and saw a section for my onboard sound card (ref line 2515): 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05) I also want to share my hw-probe output, located here: https://linux-hardware.org/?probe=13e2d05856 It appears there are approximately 50 other users utilizing the same audio driver. From my searches across a few different websites, it seems that my particular audio chip should be very well supported and simply "work". I am now thinking this is a bug, as I can't see a reason why it should be failing in this manner. Thank you for any guidance you can provide.

2 1

Fix alsa-utils building error on NetBSD
by GitHub pull_request - opened 10 Aug '21

10 Aug '21

alsa-project/alsa-lib pull request #169 was opened from triaxx: The following errors occur at least on NetBSD 9.2 amd64 when building alsa-utils: include/alsa/output.h:75:66: error: unknown type name 'va_list'; did you mean '__va_list'? include/alsa/error.h:80:25: error: unknown type name 'va_list'; did you mean '__va_list'? Request URL : https://github.com/alsa-project/alsa-lib/pull/169 Patch URL : https://github.com/alsa-project/alsa-lib/pull/169.patch Repository URL: https://github.com/alsa-project/alsa-lib

1 0

[PATCH] ASoC: dt-bindings: rt1015p: fix syntax error in dts-binding document
by Jack Yu 10 Aug '21

10 Aug '21

Fix syntax error in dts-binding document. Signed-off-by: Jack Yu <jack.yu(a)realtek.com> --- Documentation/devicetree/bindings/sound/realtek,rt1015p.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/devicetree/bindings/sound/realtek,rt1015p.yaml b/Documentation/devicetree/bindings/sound/realtek,rt1015p.yaml index 8fcb5f79a1b5..f31d3c4d0192 100644 --- a/Documentation/devicetree/bindings/sound/realtek,rt1015p.yaml +++ b/Documentation/devicetree/bindings/sound/realtek,rt1015p.yaml @@ -16,8 +16,8 @@ description: | properties: compatible: oneOf: - const: realtek,rt1015p - const: realtek,rt1019p + - const: realtek,rt1015p + - const: realtek,rt1019p sdb-gpios: description: -- 2.31.1

3 2

[PATCH 1/2] ALSA: hda: Release controller display power during shutdown/reboot
by Imre Deak 10 Aug '21

10 Aug '21

Make sure the HDA driver's display power reference is released during shutdown/reboot. During the shutdown/reboot sequence the pci device core calls the pm_runtime_resume handler for all devices before calling the driver's shutdown callback and so the HDA driver's runtime resume callback will acquire a display power reference (on HSW/BDW). This triggers a power reference held WARN on HSW/BDW in the i915 driver's subsequent shutdown handler, which expects all display power references to be released by that time. Since the HDA controller is stopped in the shutdown handler in any case, let's follow here the same sequence as the one during runtime suspend. This will also reset the HDA link and drop the display power reference, getting rid of the above WARN. Tested on HSW. v2: - Fix the build for CONFIG_PM=n (Takashi) - s/__azx_runtime_suspend/azx_shutdown_chip/ Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/3618 References: https://lore.kernel.org/lkml/cea1f9a-52e0-b83-593d-52997fe1aaf6@er-systems.… Reported-and-tested-by: Thomas Voegtle <tv(a)lio96.de> Cc: Takashi Iwai <tiwai(a)suse.de> Signed-off-by: Imre Deak <imre.deak(a)intel.com> --- sound/pci/hda/hda_intel.c | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/sound/pci/hda/hda_intel.c b/sound/pci/hda/hda_intel.c index 7f8f11536a3dc..f5ab0b682adcc 100644 --- a/sound/pci/hda/hda_intel.c +++ b/sound/pci/hda/hda_intel.c @@ -883,6 +883,14 @@ static unsigned int azx_get_pos_skl(struct azx *chip, struct azx_dev *azx_dev) return azx_get_pos_posbuf(chip, azx_dev); } +static void azx_shutdown_chip(struct azx *chip) +{ + azx_stop_chip(chip); + azx_enter_link_reset(chip); + azx_clear_irq_pending(chip); + display_power(chip, false); +} + #ifdef CONFIG_PM static DEFINE_MUTEX(card_list_lock); static LIST_HEAD(card_list); @@ -942,14 +950,6 @@ static bool azx_is_pm_ready(struct snd_card *card) return true; } -static void __azx_runtime_suspend(struct azx *chip) -{ - azx_stop_chip(chip); - azx_enter_link_reset(chip); - azx_clear_irq_pending(chip); - display_power(chip, false); -} - static void __azx_runtime_resume(struct azx *chip) { struct hda_intel *hda = container_of(chip, struct hda_intel, chip); @@ -1028,7 +1028,7 @@ static int azx_suspend(struct device *dev) chip = card->private_data; bus = azx_bus(chip); - __azx_runtime_suspend(chip); + azx_shutdown_chip(chip); if (bus->irq >= 0) { free_irq(bus->irq, chip); bus->irq = -1; @@ -1107,7 +1107,7 @@ static int azx_runtime_suspend(struct device *dev) /* enable controller wake up event */ azx_writew(chip, WAKEEN, azx_readw(chip, WAKEEN) | STATESTS_INT_MASK); - __azx_runtime_suspend(chip); + azx_shutdown_chip(chip); trace_azx_runtime_suspend(chip); return 0; } @@ -2383,7 +2383,7 @@ static void azx_shutdown(struct pci_dev *pci) return; chip = card->private_data; if (chip && chip->running) - azx_stop_chip(chip); + azx_shutdown_chip(chip); } /* PCI IDs */ -- 2.27.0

4 4

[PATCH] ALSA: hda/realtek: fix mute/micmute LEDs for HP ProBook 650 G8 Notebook PC
by Jeremy Szu 10 Aug '21

10 Aug '21

The HP ProBook 650 G8 Notebook PC is using ALC236 codec which is using 0x02 to control mute LED and 0x01 to control micmute LED. Therefore, add a quirk to make it works. Signed-off-by: Jeremy Szu <jeremy.szu(a)canonical.com> --- sound/pci/hda/patch_realtek.c | 1 + 1 file changed, 1 insertion(+) diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c index 4043a2362f27..a065260d0d20 100644 --- a/sound/pci/hda/patch_realtek.c +++ b/sound/pci/hda/patch_realtek.c @@ -8431,6 +8431,7 @@ static const struct snd_pci_quirk alc269_fixup_tbl[] = { SND_PCI_QUIRK(0x103c, 0x87f4, "HP", ALC287_FIXUP_HP_GPIO_LED), SND_PCI_QUIRK(0x103c, 0x87f5, "HP", ALC287_FIXUP_HP_GPIO_LED), SND_PCI_QUIRK(0x103c, 0x87f7, "HP Spectre x360 14", ALC245_FIXUP_HP_X360_AMP), + SND_PCI_QUIRK(0x103c, 0x8805, "HP ProBook 650 G8 Notebook PC", ALC236_FIXUP_HP_GPIO_LED), SND_PCI_QUIRK(0x103c, 0x880d, "HP EliteBook 830 G8 Notebook PC", ALC285_FIXUP_HP_GPIO_LED), SND_PCI_QUIRK(0x103c, 0x8846, "HP EliteBook 850 G8 Notebook PC", ALC285_FIXUP_HP_GPIO_LED), SND_PCI_QUIRK(0x103c, 0x8847, "HP EliteBook x360 830 G8 Notebook PC", ALC285_FIXUP_HP_GPIO_LED), -- 2.25.1

2 1