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

[PATCH] ALSA: hda/realtek: Enable headset mic on Lenovo P360
by Kai-Heng Feng 27 Mar '22

27 Mar '22

Lenovo P360 is another platform equipped with ALC897, and it needs ALC897_FIXUP_HEADSET_MIC_PIN quirk to make its headset mic work. Signed-off-by: Kai-Heng Feng <kai.heng.feng(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 e88fbef57c40c..4c33cb57963db 100644 --- a/sound/pci/hda/patch_realtek.c +++ b/sound/pci/hda/patch_realtek.c @@ -11152,6 +11152,7 @@ static const struct snd_pci_quirk alc662_fixup_tbl[] = { SND_PCI_QUIRK(0x144d, 0xc051, "Samsung R720", ALC662_FIXUP_IDEAPAD), SND_PCI_QUIRK(0x14cd, 0x5003, "USI", ALC662_FIXUP_USI_HEADSET_MODE), SND_PCI_QUIRK(0x17aa, 0x1036, "Lenovo P520", ALC662_FIXUP_LENOVO_MULTI_CODECS), + SND_PCI_QUIRK(0x17aa, 0x1057, "Lenovo P360", ALC897_FIXUP_HEADSET_MIC_PIN), SND_PCI_QUIRK(0x17aa, 0x32ca, "Lenovo ThinkCentre M80", ALC897_FIXUP_HEADSET_MIC_PIN), SND_PCI_QUIRK(0x17aa, 0x32cb, "Lenovo ThinkCentre M70", ALC897_FIXUP_HEADSET_MIC_PIN), SND_PCI_QUIRK(0x17aa, 0x32cf, "Lenovo ThinkCentre M950", ALC897_FIXUP_HEADSET_MIC_PIN), -- 2.34.1

2 1

PulseAudio only working after setting the UCM - kblda7219max on the ChromeOS Kernel, 5.10.70
by GitHub issues - opened 26 Mar '22

26 Mar '22

alsa-project/alsa-ucm-conf issue #142 was opened from MilkyDeveloper: On my `kblda7219max` Chromebook (baseboard: NAMI), internal audio works properly when the following conditions are met: * Kernel 5.10.70 (ChromeOS fork) is used (the latest ChromeOS kernel has some kind of topology-related kernel bug) * FW is copied from the ChromeOS rootfs to Linux * UCM is converted to UCM2 * Only ALSA is used However, whenever I start PulseAudio (`pulseaudio -vvvv`), audio is disabled, going to a dummy output. PulseAudio passes through probing for the UCM files but errors out in this particular spot: ``` I: [pulseaudio] (alsa-lib)pcm_hw.c: SNDRV_PCM_IOCTL_PREPARE failed (-22) I: [pulseaudio] alsa-util.c: snd_pcm_hw_params failed: Invalid argument D: [pulseaudio] alsa-util.c: Trying hw:kblda7219max,0 without SND_PCM_NO_AUTO_FORMAT ... D: [pulseaudio] alsa-util.c: Managed to open hw:kblda7219max,0 D: [pulseaudio] alsa-util.c: Maximum hw buffer size is 21845 ms I: [pulseaudio] (alsa-lib)pcm_hw.c: SNDRV_PCM_IOCTL_PREPARE failed (-22) I: [pulseaudio] (alsa-lib)pcm_hw.c: SNDRV_PCM_IOCTL_PREPARE failed (-22) I: [pulseaudio] (alsa-lib)pcm_hw.c: SNDRV_PCM_IOCTL_PREPARE failed (-22) I: [pulseaudio] (alsa-lib)pcm_hw.c: SNDRV_PCM_IOCTL_PREPARE failed (-22) ``` which causes it to say: ``` E: [pulseaudio] module-alsa-card.c: Failed to find a working profile. E: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="0" name="platform-kbl_da7219_mx98357a" card_name="alsa_card.platform-kbl_da7219_mx98357a" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed. ``` My `dmesg` gets filled with: ``` Kbl Audio Port: ASoC: no backend DAIs enabled for Kbl Audio Port Kbl Audio Port: ASoC: dpcm_fe_dai_prepare() failed (-22) ``` However, once I kill PulseAudio and run `alsaucm -c kblda7219max set _verb HiFi set _enadev Speaker`, audio begins working again (but this is in pure ALSA and PA apps are not compatible) and the `no backend DAIs enabled for Kbl Audio Port` is no longer logged to `dmesg`. I think this is a UCM issue because the audio is working fine kernel-level and with ALSA, but PulseAudio seems to mess something up with the UCM and the UCM needs to be set again. Huge thanks for any help! [alsa-info.txt](https://github.com/alsa-project/alsa-ucm-conf/files/8355612/… (My PulseAudio log is slightly different from the time I ran PulseAudio and got the PCM_IOCTL_PREPARE error) [pulseaudio-log.txt](https://github.com/alsa-project/alsa-ucm-conf/files/835… [HiFi.conf.txt](https://github.com/alsa-project/alsa-ucm-conf/files/8355631/… [kblda7219max.conf.txt](https://github.com/alsa-project/alsa-ucm-conf/files/… Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/142 Repository URL: https://github.com/alsa-project/alsa-ucm-conf

1 0

Conceptual bug on SoundWire probe/remove?
by Pierre-Louis Bossart 26 Mar '22

26 Mar '22

Hi, I could use feedback/guidance on a possible conceptual bug in the SoundWire probe and bus handling. When we probe a driver, the code does this: static int sdw_drv_probe(struct device *dev) { struct sdw_slave *slave = dev_to_sdw_dev(dev); struct sdw_driver *drv = drv_to_sdw_driver(dev->driver); const struct sdw_device_id *id; const char *name; int ret; /* * fw description is mandatory to bind */ if (!dev->fwnode) return -ENODEV; if (!IS_ENABLED(CONFIG_ACPI) && !dev->of_node) return -ENODEV; id = sdw_get_device_id(slave, drv); if (!id) return -ENODEV; slave->ops = drv->ops; The last line is the problematic one. If at some point, the user does an rmmod and unbinds the SoundWire codec driver, the .remove will be called and the 'drv' will no longer be valid, but we will still have a reference to drv->ops and use that pointer in the bus code, e.g. /* Update the Slave driver */ if (slave_notify && slave->ops && slave->ops->interrupt_callback) { slave_intr.sdca_cascade = sdca_cascade; slave_intr.control_port = clear; memcpy(slave_intr.port, &port_status, sizeof(slave_intr.port)); slave->ops->interrupt_callback(slave, &slave_intr); } I noodled with a potential fix in https://github.com/thesofproject/linux/pull/3534/commits/82d64fb0fd39b53226… where I force-reset this slave->ops pointer, but it is likely to be very racy. We probably need to avoid such references, or have a clean mechanism to unbind, e.g. with all commands and interrupts stopped while the codec driver .remove routine is handled. Initial error reports at https://github.com/thesofproject/linux/issues/3531 Suggestions and comments welcome, thanks! -Pierre

5 8

[PATCH] ASoC: codecs: add support for ES8326 dts
by zhuning＠everest-semi.com 26 Mar '22

26 Mar '22

From: yangxiaohua <yangxiaohua(a)everest-semi.com> Subject: [PATCH 1/1] ASoC: codecs: add support for ES8326 dts The ES8326 codec is not compatible with ES8316 and requires a dedicated driver. This is a separate patch for ES8326 dts Signed-off-by: David Yang <yangxiaohua(a)everest-semi.com> --- .../bindings/sound/everest,es8326.yaml | 109 ++++++++++++++++++ 1 file changed, 109 insertions(+) create mode 100755 Documentation/devicetree/bindings/sound/everest,es8326.yaml diff --git a/Documentation/devicetree/bindings/sound/everest,es8326.yaml b/Documentation/devicetree/bindings/sound/everest,es8326.yaml new file mode 100755 index 000000000000..8cae9c328dbc --- /dev/null +++ b/Documentation/devicetree/bindings/sound/everest,es8326.yaml @@ -0,0 +1,109 @@ +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/sound/everest,es8326.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Everest ES8326 audio CODEC + +maintainers: + - David Yang <yangxiaohua(a)everest-semi.com> + +properties: + compatible: + const: everest,es8326 + + reg: + maxItems: 1 + + clocks: + items: + - description: clock for master clock (MCLK) + + clock-names: + items: + - const: mclk + + "#sound-dai-cells": + const: 0 + + mclk-rate: + description: + clock rate of mclk + $ref: /schemas/types.yaml#/definitions/uint32-array + minItems: 1 + + everest,jack-pol: + description: + just the value of reg 57. Bit(3) decides whether the jack polarity is inverted. + Bit(2) decides whether the bottom on the headset is inverted. + Bit(1)/(0) decides the mic properity to be OMTP/CTIA or auto. + $ref: /schemas/types.yaml#/definitions/uint8-array + minimum: 0 + maximum: 0x0f + default: 0x0f + + everest,mic1-src: + description: + the value of reg 2A when headset plugged. + $ref: /schemas/types.yaml#/definitions/uint8-array + minimum: 0x00 + maximum: 0x77 + default: 0x22 + + everest,mic2-src: + description: + the value of reg 2A when headset unplugged. + $ref: /schemas/types.yaml#/definitions/uint8-array + minimum: 0x00 + maximum: 0x77 + default: 0x44 + + everest,amic1-src: + description: + the value of reg 23 when headset plugged. + $ref: /schemas/types.yaml#/definitions/uint8-array + minimum: 0x19 + maximum: 0x29 + default: 0x19 + + everest,amic2-src: + description: + the value of reg 23 when headset unplugged. + Set to 0x19 if dmic used. Set to 0x29 if amic used. + $ref: /schemas/types.yaml#/definitions/uint8-array + minimum: 0x19 + maximum: 0x29 + default: 0x19 + + everest,jack-detect-inverted: + description: + Defined to invert the jack detection. + $ref: /schemas/types.yaml#/definitions/flag + +required: + - compatible + - reg + - "#sound-dai-cells" + + +additionalProperties: false + +examples: + - | + i2c0 { + #address-cells = <1>; + #size-cells = <0>; + es8326: codec@19 { + compatible = "everest,es8326"; + reg = <0x19>; + clocks = <&clks 10>; + clock-names = "mclk"; + #sound-dai-cells = <0>; + mic1-src = [22]; + mic2-src = [44]; + amic1-src = [19]; + amic2-src = [19]; + jack-pol = [0e]; + }; + }; -- 2.17.1

1 0

Add UCM for PinePhone
by GitHub pull_request - edited 26 Mar '22

26 Mar '22

alsa-project/alsa-ucm-conf pull request #134 was edited from tomfitzhenry: Fixes https://github.com/alsa-project/alsa-ucm-conf/issues/124. This PR adds support for the https://wiki.pine64.org/index.php/PinePhone This PR contains: * This UCM config copied from https://gitlab.com/pine64-org/pine64-alsa-ucm/, which was developed by many developers ( https://gitlab.com/pine64-org/pine64-alsa-ucm/-/merge_requests/1 ) and is BSD-3-Clause licensed. * Fix paths to be relative to alsa-ucm-conf root. * Some refactoring of the UCM config, incl. removing duplicate directives, and moving volume directives to BootSequence. * Updating the routing/playback/boost volumes, in response to comments on this PR. I have tested: * HiFi * Record audio via the headset. * Record audio via the internal mic. * Play audio on the headphones. * Play audio on the speaker. * Play audio on the internal speaker. * Voice Call * Speak on the headset. * Speak on the internal mic. * Listen on the headphones. * Listen on the speaker. This induces an echo, and given the audio routing is entirely on chip, and the chip doesn't advertise echo cancellation, I don't see how this is avoidable. * Listen on the internal speaker. See also: * `alsa-info`: https://alsa-project.org/db/?f=5e331f5ef10bd167b3bd7640bfcf0e879100f80d * `pa-info`: [pa-info.txt](https://github.com/alsa-project/alsa-ucm-conf/files/8015083/pa… * https://gitlab.com/pine64-org/pine64-alsa-ucm/-/issues/3 * Schematics/code * The device-tree configuration has had a unique audio card name since 5.14: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arc… * http://files.pine64.org/doc/PinePhone/PinePhone%20v1.2%20Released%20Schemat… * https://xnux.eu/devices/feature/audio-pp.html * https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/allwinner… * https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/allwinner… * https://github.com/torvalds/linux/blob/master/sound/soc/sunxi/sun50i-codec-… * https://files.pine64.org/doc/datasheet/pine64/Allwinner_A64_User_Manual_V1.… * https://static.chipdip.ru/lib/126/DOC001126567.pdf Request URL : https://github.com/alsa-project/alsa-ucm-conf/pull/134 Patch URL : https://github.com/alsa-project/alsa-ucm-conf/pull/134.patch Repository URL: https://github.com/alsa-project/alsa-ucm-conf

1 0

Add UCM for PinePhone
by GitHub pull_request - edited 26 Mar '22

26 Mar '22

alsa-project/alsa-ucm-conf pull request #134 was edited from tomfitzhenry: Fixes https://github.com/alsa-project/alsa-ucm-conf/issues/124. This PR adds support for the https://wiki.pine64.org/index.php/PinePhone This PR contains: * This UCM config copied from https://gitlab.com/pine64-org/pine64-alsa-ucm/, which was developed by many developers ( https://gitlab.com/pine64-org/pine64-alsa-ucm/-/merge_requests/1 ) and is BSD-3-Clause licensed. * Fix paths to be relative to alsa-ucm-conf root. * Some refactoring of the UCM config, incl. removing duplicate directives, and moving volume directives to BootSequence. * Updating the playback/boost volumes, in response to comments on this PR. I have tested: * HiFi * Record audio via the headset. * Record audio via the internal mic. * Play audio on the headphones. * Play audio on the speaker. * Play audio on the internal speaker. * Voice Call * Speak on the headset. * Speak on the internal mic. * Listen on the headphones. * Listen on the speaker. This induces an echo, and given the audio routing is entirely on chip, and the chip doesn't advertise echo cancellation, I don't see how this is avoidable. * Listen on the internal speaker. See also: * `alsa-info`: https://alsa-project.org/db/?f=5e331f5ef10bd167b3bd7640bfcf0e879100f80d * `pa-info`: [pa-info.txt](https://github.com/alsa-project/alsa-ucm-conf/files/8015083/pa… * https://gitlab.com/pine64-org/pine64-alsa-ucm/-/issues/3 * Schematics/code * The device-tree configuration has had a unique audio card name since 5.14: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arc… * http://files.pine64.org/doc/PinePhone/PinePhone%20v1.2%20Released%20Schemat… * https://xnux.eu/devices/feature/audio-pp.html * https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/allwinner… * https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/allwinner… * https://github.com/torvalds/linux/blob/master/sound/soc/sunxi/sun50i-codec-… * https://files.pine64.org/doc/datasheet/pine64/Allwinner_A64_User_Manual_V1.… * https://static.chipdip.ru/lib/126/DOC001126567.pdf Request URL : https://github.com/alsa-project/alsa-ucm-conf/pull/134 Patch URL : https://github.com/alsa-project/alsa-ucm-conf/pull/134.patch Repository URL: https://github.com/alsa-project/alsa-ucm-conf

1 0

[PATCH -next] ASoC: SOF: Intel: Fix build error without SND_SOC_SOF_PCI_DEV
by Zheng Bin 25 Mar '22

25 Mar '22

If SND_SOC_SOF_PCI_DEV is n, bulding fails: sound/soc/sof/intel/pci-tng.o:(.data+0x1c0): undefined reference to `sof_pci_probe' sound/soc/sof/intel/pci-tng.o:(.data+0x1c8): undefined reference to `sof_pci_remove' sound/soc/sof/intel/pci-tng.o:(.data+0x1e0): undefined reference to `sof_pci_shutdown' sound/soc/sof/intel/pci-tng.o:(.data+0x290): undefined reference to `sof_pci_pm' Make SND_SOC_SOF_MERRIFIELD select SND_SOC_SOF_PCI_DEV to fix this. Fixes: 8d4ba1be3d22 ("ASoC: SOF: pci: split PCI into different drivers") Reported-by: Hulk Robot <hulkci(a)huawei.com> Signed-off-by: Zheng Bin <zhengbin13(a)huawei.com> --- sound/soc/sof/intel/Kconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/sound/soc/sof/intel/Kconfig b/sound/soc/sof/intel/Kconfig index b53f216d4ecc..172419392b33 100644 --- a/sound/soc/sof/intel/Kconfig +++ b/sound/soc/sof/intel/Kconfig @@ -84,6 +84,7 @@ if SND_SOC_SOF_PCI config SND_SOC_SOF_MERRIFIELD tristate "SOF support for Tangier/Merrifield" default SND_SOC_SOF_PCI + select SND_SOC_SOF_PCI_DEV select SND_SOC_SOF_INTEL_ATOM_HIFI_EP help This adds support for Sound Open Firmware for Intel(R) platforms -- 2.31.1

3 2

[PATCH] ASoC: rt5682s: Separate the regulator consumer controls
by derek.fang＠realtek.com 25 Mar '22

25 Mar '22

From: Derek Fang <derek.fang(a)realtek.com> Control the regulators separately instead of using regulator_bulk to accord to the timing request in the datasheet. Signed-off-by: Derek Fang <derek.fang(a)realtek.com> --- sound/soc/codecs/rt5682s.c | 26 +++++++++++++++++++++----- sound/soc/codecs/rt5682s.h | 6 +++++- 2 files changed, 26 insertions(+), 6 deletions(-) diff --git a/sound/soc/codecs/rt5682s.c b/sound/soc/codecs/rt5682s.c index 1cba8ec7cedb..b8bf9aede29c 100644 --- a/sound/soc/codecs/rt5682s.c +++ b/sound/soc/codecs/rt5682s.c @@ -42,8 +42,8 @@ static const struct rt5682s_platform_data i2s_default_platform_data = { }; static const char *rt5682s_supply_names[RT5682S_NUM_SUPPLIES] = { - "AVDD", - "MICVDD", + [RT5682S_SUPPLY_AVDD] = "AVDD", + [RT5682S_SUPPLY_MICVDD] = "MICVDD", }; static const struct reg_sequence patch_list[] = { @@ -3025,8 +3025,17 @@ static struct snd_soc_dai_driver rt5682s_dai[] = { static void rt5682s_i2c_disable_regulators(void *data) { struct rt5682s_priv *rt5682s = data; + int ret; + + ret = regulator_disable(rt5682s->supplies[RT5682S_SUPPLY_AVDD].consumer); + if (ret) + pr_err("%s: Failed to disable supply AVDD: %d\n", __func__, ret); - regulator_bulk_disable(ARRAY_SIZE(rt5682s->supplies), rt5682s->supplies); + usleep_range(1000, 1500); + + ret = regulator_disable(rt5682s->supplies[RT5682S_SUPPLY_MICVDD].consumer); + if (ret) + pr_err("%s: Failed to disable supply MICVDD: %d\n", __func__, ret); } static int rt5682s_i2c_probe(struct i2c_client *i2c, @@ -3071,9 +3080,16 @@ static int rt5682s_i2c_probe(struct i2c_client *i2c, if (ret) return ret; - ret = regulator_bulk_enable(ARRAY_SIZE(rt5682s->supplies), rt5682s->supplies); + ret = regulator_enable(rt5682s->supplies[RT5682S_SUPPLY_MICVDD].consumer); + if (ret) { + dev_err(&i2c->dev, "Failed to enable supply MICVDD: %d\n", ret); + return ret; + } + usleep_range(1000, 1500); + + ret = regulator_enable(rt5682s->supplies[RT5682S_SUPPLY_AVDD].consumer); if (ret) { - dev_err(&i2c->dev, "Failed to enable supplies: %d\n", ret); + dev_err(&i2c->dev, "Failed to enable supply AVDD: %d\n", ret); return ret; } diff --git a/sound/soc/codecs/rt5682s.h b/sound/soc/codecs/rt5682s.h index 397a2531b6f6..7353831c73dd 100644 --- a/sound/soc/codecs/rt5682s.h +++ b/sound/soc/codecs/rt5682s.h @@ -1434,7 +1434,11 @@ struct pll_calc_map { bool sel_ps; }; -#define RT5682S_NUM_SUPPLIES 2 +enum { + RT5682S_SUPPLY_AVDD, + RT5682S_SUPPLY_MICVDD, + RT5682S_NUM_SUPPLIES, +}; struct rt5682s_priv { struct snd_soc_component *component; -- 2.17.1

2 1

[PATCH v2 1/2] ASoC: bindings: fsl-asoc-card: Add compatible for tlv320aic31xx codec
by Ariel D'Alessandro 25 Mar '22

25 Mar '22

Commit 8c9b9cfb7724 ("ASoC: fsl-asoc-card: Support fsl,imx-audio-tlv320aic31xx codec")' added support for tlv320aic31xx codec to fsl-asoc-card, but missed the related device-tree compatible string documentation. Fix this. Signed-off-by: Ariel D'Alessandro <ariel.dalessandro(a)collabora.com> --- Documentation/devicetree/bindings/sound/fsl-asoc-card.txt | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Documentation/devicetree/bindings/sound/fsl-asoc-card.txt b/Documentation/devicetree/bindings/sound/fsl-asoc-card.txt index b219626a5403..8b4f4015cfe4 100644 --- a/Documentation/devicetree/bindings/sound/fsl-asoc-card.txt +++ b/Documentation/devicetree/bindings/sound/fsl-asoc-card.txt @@ -40,6 +40,8 @@ The compatible list for this generic sound card currently: "fsl,imx-audio-tlv320aic32x4" + "fsl,imx-audio-tlv320aic31xx" + "fsl,imx-audio-si476x" "fsl,imx-audio-wm8958" -- 2.34.1

4 7

Re: Apogee ONEv2 keeps resetting
by Alan Stern 24 Mar '22

24 Mar '22

On Thu, Mar 24, 2022 at 03:44:41AM +0100, Petr Janecek wrote: > Hi Alan, > > On 3/22/22 19:03, Alan Stern wrote: > > On Sun, Mar 20, 2022 at 02:15:40AM +0100, Petr Janecek wrote: > > > Hi, > > > I'm trying to use Apogee ONEv2. From usb dumps under > > > macos or windows it seems like a usb Class Audio 2.0 > > > device, but in linux, it keeps resetting every two seconds > > > or so. It keeps resetting even when the snd-usb-audio > > > driver is disabled, so the problem is probably at a lower > > > level. > > > > Can you post the log output on a system where snd-usb-audio is disabled? > > [ 3412.279063] usb 3-8: new high-speed USB device number 6 using xhci_hcd > [ 3412.470003] usb 3-8: New USB device found, idVendor=0c60, idProduct=0017, > bcdDevice= 1.05 > [ 3412.470017] usb 3-8: New USB device strings: Mfr=1, Product=2, > SerialNumber=3 > [ 3412.470023] usb 3-8: Product: ONEv2 > [ 3412.470028] usb 3-8: Manufacturer: Apogee > [ 3412.470033] usb 3-8: SerialNumber: 0C12FF2020204652334D513A7A2A9B > [ 3413.217053] usb 3-8: USB disconnect, device number 6 > [ 3413.629046] usb 3-8: new high-speed USB device number 7 using xhci_hcd > [ 3413.829760] usb 3-8: New USB device found, idVendor=0c60, idProduct=0017, > bcdDevice= 1.05 > [ 3413.829766] usb 3-8: New USB device strings: Mfr=1, Product=2, > SerialNumber=3 > [ 3413.829768] usb 3-8: Product: ONEv2 > [ 3413.829770] usb 3-8: Manufacturer: Apogee > [ 3413.829772] usb 3-8: SerialNumber: 0C12FF2020204652334D513A7A2A9B > [ 3414.421964] usb 3-8: USB disconnect, device number 7 > [ 3414.838981] usb 3-8: new high-speed USB device number 8 using xhci_hcd > [ 3415.029947] usb 3-8: New USB device found, idVendor=0c60, idProduct=0017, > bcdDevice= 1.05 > [ 3415.029961] usb 3-8: New USB device strings: Mfr=1, Product=2, > SerialNumber=3 > [ 3415.029968] usb 3-8: Product: ONEv2 > [ 3415.029973] usb 3-8: Manufacturer: Apogee > [ 3415.029978] usb 3-8: SerialNumber: 0C12FF2020204652334D513A7A2A9B > [ 3415.627052] usb 3-8: USB disconnect, device number 8 Nothing particularly suspicious there. > > > > The messages below are from v5.16.16, but it behaves > > > the same no matter what I plug it into. > > > > > > [ 253.708616] usb 3-8: new high-speed USB device number 6 using xhci_hcd > > > [ 253.899363] usb 3-8: New USB device found, idVendor=0c60, idProduct=0017, > > > bcdDevice= 1.05 > > > [ 253.899370] usb 3-8: New USB device strings: Mfr=1, Product=2, > > > SerialNumber=3 > > > [ 253.899373] usb 3-8: Product: ONEv2 > > > [ 253.899375] usb 3-8: Manufacturer: Apogee > > > [ 253.899377] usb 3-8: SerialNumber: 0C12FF2020204652334D513A7A2A9B > > > [ 253.960901] mc: Linux media interface: v0.10 > > > > Any idea where that line came from? > > That's from CONFIG_MEDIA_CONTROLLER, which is selected for usb > webcam. It also selects CONFIG_SND_USB_AUDIO_USE_MEDIA_CONTROLLER. > Compiled it out, rebooted. Now the line is missing, but no other > change. > > > You should try capturing a usbmon trace showing what happens when the > > device is plugged in and then resets. Preferably on a system where > > snd-usb-audio is disabled. > > Trace from wireshark is attached. The trace doesn't help much, unfortunately. It shows normal device initialization, plus a couple of extra string descriptor reads. About 1/2 second afterward, the device disconnects itself electronically from the USB bus and reconnects 20 ms later. I get the feeling that the device expects to receive some specific messages from the host within that one-half second, and disconnects if it doesn't see them. And presumably it doesn't get what it's looking for even when the USB sound drivers are enabled. Although I doubt it will show anything helpful, you might try collecting a usbmon trace with the sound drivers enabled. Perhaps it will suggest something to the USB audio developers. > > One other thing you might try: Disable runtime PM for USB ("echo -1 > > > /sys/module/usbcore/parameters/autosuspend" before plugging in the > > device). > > Makes no difference -- almost: after few resets it once took much > longer (>10x) to reconnect. Oh well, it was worth a try. Some devices don't like runtime suspend. But obviously that isn't the problem here. Alan Stern

1 0