From: GitHub issues - edited <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: microphone disappeared on alsa-ucm-conf 1.2.6.1
Date: Thu, 9 Dec 2021 23:06:07 +0100 (CET) [thread overview]
Message-ID: <20211209220607.54524F804AE@alsa1.perex.cz> (raw)
In-Reply-To: <1639087560992140055-webhooks-bot@alsa-project.org>
alsa-project/alsa-lib issue #200 was edited from galibozek:
after upgrade alsa-ucm-conf 1.2.5.1-1 to 1.2.6.1-1 (arch linux) my microphone disappeared on lenovo t14 gen2i
Similar to: https://bugs.archlinux.org/task/71180
```
00:1f.3 Audio device: Intel Corporation Tiger Lake-LP Smart Sound Technology Audio Controller (rev 20) (prog-if 80)
Subsystem: Lenovo Device 22c9
Flags: bus master, fast devsel, latency 64, IRQ 187, IOMMU group 12
Memory at 603dbc0000 (64-bit, non-prefetchable) [size=16K]
Memory at 603da00000 (64-bit, non-prefetchable) [size=1M]
Capabilities: <access denied>
Kernel driver in use: sof-audio-pci-intel-tgl
Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl
```
Issue URL : https://github.com/alsa-project/alsa-lib/issues/200
Repository URL: https://github.com/alsa-project/alsa-lib
next parent reply other threads:[~2021-12-09 22:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1639087560992140055-webhooks-bot@alsa-project.org>
2021-12-09 22:06 ` GitHub issues - edited [this message]
[not found] <1639088550468589067-webhooks-bot@alsa-project.org>
2021-12-09 22:22 ` microphone disappeared on alsa-ucm-conf 1.2.6.1 GitHub issues - edited
[not found] <1639087486438345909-webhooks-bot@alsa-project.org>
2021-12-09 22:04 ` GitHub issues - edited
[not found] <1639087256810755014-webhooks-bot@alsa-project.org>
2021-12-09 22:01 ` GitHub issues - edited
[not found] <1639087179268137932-webhooks-bot@alsa-project.org>
2021-12-09 21:59 ` GitHub issues - edited
[not found] <1639087091620373964-webhooks-bot@alsa-project.org>
2021-12-09 21:58 ` GitHub issues - edited
[not found] <1639087060331087112-webhooks-bot@alsa-project.org>
2021-12-09 21:57 ` GitHub issues - opened
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211209220607.54524F804AE@alsa1.perex.cz \
--to=github@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.