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

Re: Fw: [External] RE: [PATCH -next] ASoC: amd: yc: Adding Lenovo ThinkBook 14 Gen 4+ ARA and Lenovo ThinkBook 16 Gen 4+ ARA to the Quirks List
by Mark Pearson 11 Oct '22

11 Oct '22

<moved to my more open-source friendly email account> Thanks Mario On 2022-10-11 13:14, Mark Pearson wrote: > > -------------------------------------------------------------------------------- > *From:* Limonciello, Mario <Mario.Limonciello(a)amd.com> > *Sent:* October 11, 2022 13:08 > *Subject:* [External] RE: [PATCH -next] ASoC: amd: yc: Adding Lenovo ThinkBook > 14 Gen 4+ ARA and Lenovo ThinkBook 16 Gen 4+ ARA to the Quirks List > [Public] > > Cc: > Mark Pearson > Vijendar > Syed > Renjith > >> -----Original Message----- >> From: linkt <xazrael(a)hotmail.com> >> Sent: Monday, October 10, 2022 21:52 >> To: lgirdwood(a)gmail.com; broonie(a)kernel.org; perex(a)perex.cz; >> tiwai(a)suse.com; Limonciello, Mario <Mario.Limonciello(a)amd.com> >> Cc: alsa-devel(a)alsa-project.org; linux-kernel(a)vger.kernel.org; linkt >> <xazrael(a)hotmail.com> >> Subject: [PATCH -next] ASoC: amd: yc: Adding Lenovo ThinkBook 14 Gen 4+ >> ARA and Lenovo ThinkBook 16 Gen 4+ ARA to the Quirks List >> >> Lenovo ThinkBook 14 Gen 4+ ARA and ThinkBook 16 Gen 4+ ARA >> need to be added to the list of quirks for the microphone to work properly. >> >> Signed-off-by: linkt <xazrael(a)hotmail.com> > > This patch alone makes sense to me. > > Cc: stable(a)vger.kernel.org > Reviewed-by: Mario Limonciello <mario.limonciello(a)amd.com> > > I think it should go in as is, but it prompts another idea to me I want to run by > Mark specifically.. > > Should we just drop this whole file down to a much simpler DMI match prefix like > this: > >> + { >> + .driver_data = &acp6x_card, >> + .matches = { >> + DMI_MATCH(DMI_BOARD_VENDOR, "LENOVO"), >> + DMI_MATCH(DMI_PRODUCT_NAME, "21"), >> + } >> + }, > > That would allow it to match all the Lenovo Rembrandt systems presumably and > can stop touching the file. This only makes sense if every single Lenovo > Rembrandt design > uses a DMIC from ACP. I don't know if that's a valid assumption and I think we > need Mark > to confirm it. > > The DMI match "technically" would match some of the Intel systems from this > generation > but this driver is only "loaded" on AMD Rembrandt systems, so I don't think it's > a problem. > I love the idea but I'm a little hesitant as I don't know if I'll be able to confirm it authoritatively - I don't have particularly great levers to pull on for platforms outside the Linux program. I'll try - but I think chances of being able to reply yes or no with confidence are limited. I think it's relatively low risk for breaking anything on this years platforms - but may get more interesting for next years. If needed can we then just quirk any platforms that come up that need the logic reversing or does that get really messy. I can confirm the "21" match is going to be match a ton of Intel platforms. For the AMD platforms - will this be limited to Rembrandt only or will it affect any past/future generations? Short answer - I'll see what I can find...but no promises Mark

2 1

Re: [PATCH v2 02/36] gpiolib: cdev: Add missed header(s)
by Andy Shevchenko 11 Oct '22

11 Oct '22

On Tue, Oct 11, 2022 at 11:05:42AM +0300, Andy Shevchenko wrote: > On Tue, Oct 11, 2022 at 3:02 AM Kent Gibson <warthog618(a)gmail.com> wrote: > > On Mon, Oct 10, 2022 at 11:14:18PM +0300, Andy Shevchenko wrote: ... > > > -#include <linux/gpio.h> > > > #include <linux/gpio/driver.h> > > > +#include <linux/gpio.h> > > > +#include <linux/hte.h> > > > > Ok with the hte re-order. > > > > But moving the gpio subsystem header after the gpio/driver is not > > alphabetical ('.' precedes '/') and it read better and made more sense > > to me the way it was. > > I see, I guess this is vim sort vs shell sort. Strange, they should > follow the locale settings... I have checked, the shell and vim sort gave the same result as in this patch. -- With Best Regards, Andy Shevchenko

3 5

Add support for listing compress devices
by GitHub issues - opened 11 Oct '22

11 Oct '22

alsa-project/tinycompress issue #17 was opened from dbaluta: Similar with `aplay -l` we need an option to list compress devices. `cplay -l`. Issue URL : https://github.com/alsa-project/tinycompress/issues/17 Repository URL: https://github.com/alsa-project/tinycompress

1 0

[PATCH 1/2] ALSA: rawmidi: Drop register_mutex in snd_rawmidi_free()
by Takashi Iwai 11 Oct '22

11 Oct '22

The register_mutex taken around the dev_unregister callback call in snd_rawmidi_free() may potentially lead to a mutex deadlock, when OSS emulation and a hot unplug are involved. Since the mutex doesn't protect the actual race (as the registration itself is already protected by another means), let's drop it. Link: https://lore.kernel.org/r/CAB7eexJP7w1B0mVgDF0dQ+gWor7UdkiwPczmL7pn91xx8xpz… Cc: <stable(a)vger.kernel.org> Signed-off-by: Takashi Iwai <tiwai(a)suse.de> --- sound/core/rawmidi.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/sound/core/rawmidi.c b/sound/core/rawmidi.c index 6963d5a487b3..d8edb6055072 100644 --- a/sound/core/rawmidi.c +++ b/sound/core/rawmidi.c @@ -1899,10 +1899,8 @@ static int snd_rawmidi_free(struct snd_rawmidi *rmidi) snd_info_free_entry(rmidi->proc_entry); rmidi->proc_entry = NULL; - mutex_lock(&register_mutex); if (rmidi->ops && rmidi->ops->dev_unregister) rmidi->ops->dev_unregister(rmidi); - mutex_unlock(&register_mutex); snd_rawmidi_free_substreams(&rmidi->streams[SNDRV_RAWMIDI_STREAM_INPUT]); snd_rawmidi_free_substreams(&rmidi->streams[SNDRV_RAWMIDI_STREAM_OUTPUT]); -- 2.35.3

1 1

[PATCH] ALSA: hda/realtek: Add Intel Reference SSID to support headset keys
by Saranya Gopal 11 Oct '22

11 Oct '22

This patch fixes the issue with 3.5mm headset keys on RPL-P platform. Signed-off-by: Saranya Gopal <saranya.gopal(a)intel.com> Signed-off-by: Ninad Naik <ninad.naik(a)intel.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 bce82b834cec..4ea07634548d 100644 --- a/sound/pci/hda/patch_realtek.c +++ b/sound/pci/hda/patch_realtek.c @@ -9444,6 +9444,7 @@ static const struct snd_pci_quirk alc269_fixup_tbl[] = { SND_PCI_QUIRK(0x10ec, 0x118c, "Medion EE4254 MD62100", ALC256_FIXUP_MEDION_HEADSET_NO_PRESENCE), SND_PCI_QUIRK(0x10ec, 0x1230, "Intel Reference board", ALC295_FIXUP_CHROME_BOOK), SND_PCI_QUIRK(0x10ec, 0x1252, "Intel Reference board", ALC295_FIXUP_CHROME_BOOK), + SND_PCI_QUIRK(0x10ec, 0x124c, "Intel Reference board", ALC295_FIXUP_CHROME_BOOK), SND_PCI_QUIRK(0x10ec, 0x1254, "Intel Reference board", ALC295_FIXUP_CHROME_BOOK), SND_PCI_QUIRK(0x10f7, 0x8338, "Panasonic CF-SZ6", ALC269_FIXUP_HEADSET_MODE), SND_PCI_QUIRK(0x144d, 0xc109, "Samsung Ativ book 9 (NP900X3G)", ALC269_FIXUP_INV_DMIC), -- 2.25.1

2 1

If system has Dmic, variable DeviceDmic will be empty
by GitHub pull_request - opened 11 Oct '22

11 Oct '22

alsa-project/alsa-ucm-conf pull request #228 was opened from xanthein: change condition from False to True to configure Dmic0 correctly Request URL : https://github.com/alsa-project/alsa-ucm-conf/pull/228 Patch URL : https://github.com/alsa-project/alsa-ucm-conf/pull/228.patch Repository URL: https://github.com/alsa-project/alsa-ucm-conf

1 0

[PATCH v2] ASoC: wm8731: fix build when I2C is not enabled
by Randy Dunlap 11 Oct '22

11 Oct '22

Building wm8731-i2c.c has a kconfig warning and build errors when I2C is not enabled, so prevent that kconfig-uration. WARNING: unmet direct dependencies detected for SND_SOC_WM8731_I2C Depends on [n]: SOUND [=y] && !UML && SND [=m] && SND_SOC [=m] && I2C [=n] Selected by [m]: - SND_SOC_DB1200 [=m] && SOUND [=y] && !UML && SND [=m] && SND_SOC [=m] && SND_SOC_AU1XPSC [=m] and subsequent build errors: ../sound/soc/codecs/wm8731-i2c.c:64:1: warning: data definition has no type or storage class 64 | module_i2c_driver(wm8731_i2c_driver); ../sound/soc/codecs/wm8731-i2c.c:64:1: error: type defaults to 'int' in declaration of 'module_i2c_driver' [-Werror=implicit-int] ../sound/soc/codecs/wm8731-i2c.c:64:1: warning: parameter names (without types) in function declaration ../sound/soc/codecs/wm8731-i2c.c:55:26: warning: 'wm8731_i2c_driver' defined but not used [-Wunused-variable] 55 | static struct i2c_driver wm8731_i2c_driver = { Fixes: 9dc15f81baf2 ("ASoC: wm8731: Factor out the I2C and SPI bus code into separate modules") Reported-by: kernel test robot <lkp(a)intel.com> Signed-off-by: Randy Dunlap <rdunlap(a)infradead.org> Cc: Mark Brown <broonie(a)kernel.org> Cc: Liam Girdwood <lgirdwood(a)gmail.com> Cc: alsa-devel(a)alsa-project.org Cc: Jaroslav Kysela <perex(a)perex.cz> Cc: Takashi Iwai <tiwai(a)suse.com> --- v2: add Takashi's email address sound/soc/au1x/Kconfig | 1 + 1 file changed, 1 insertion(+) diff sound/soc/au1x/Kconfig sound/soc/au1x/Kconfig --- a/sound/soc/au1x/Kconfig +++ b/sound/soc/au1x/Kconfig @@ -54,6 +54,7 @@ config SND_SOC_DB1000 config SND_SOC_DB1200 tristate "DB1200/DB1300/DB1550 Audio support" depends on SND_SOC_AU1XPSC + depends on I2C select SND_SOC_AU1XPSC_AC97 select SND_SOC_AC97_CODEC select SND_SOC_WM9712

1 0

[PATCH] Fixes bc2c23549ccd ("ALSA: hda/realtek: Add pincfg for ASUS G533Z HP jack")
by Luke D. Jones 10 Oct '22

10 Oct '22

The initial fix for ASUS G533Z was based on faulty information. This fixes the pincfg to values that have been verified with no existing module options or other hacks enabled. Enables headphone jack, and 5.1 surround. Signed-off-by: Luke D. Jones <luke(a)ljones.dev> --- sound/pci/hda/patch_realtek.c | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c index bce82b834cec..24406f81da27 100644 --- a/sound/pci/hda/patch_realtek.c +++ b/sound/pci/hda/patch_realtek.c @@ -8449,11 +8449,13 @@ static const struct hda_fixup alc269_fixups[] = { [ALC285_FIXUP_ASUS_G533Z_PINS] = { .type = HDA_FIXUP_PINS, .v.pins = (const struct hda_pintbl[]) { - { 0x14, 0x90170120 }, - { } + { 0x14, 0x90170152 }, /* Speaker Surround Playback Switch */ + { 0x19, 0x03a19020 }, /* Mic Boost Volume */ + { 0x1a, 0x03a11c30 }, /* Mic Boost Volume */ + { 0x1e, 0x90170151 }, /* Rear jack, IN OUT EAPD Detect */ + { 0x21, 0x03211420 }, + { } }, - .chained = true, - .chain_id = ALC294_FIXUP_ASUS_G513_PINS, }, [ALC294_FIXUP_ASUS_COEF_1B] = { .type = HDA_FIXUP_VERBS, -- 2.37.3

3 2

topology: nhlt: intel: ssp: fix obvious typo for 'codec_provider'
by GitHub pull_request - opened 10 Oct '22

10 Oct '22

alsa-project/alsa-utils pull request #174 was opened from plbossart: Looks like a bad search and replace? Signed-off-by: Pierre-Louis Bossart <pierre-louis.bossart(a)linux.intel.com> Request URL : https://github.com/alsa-project/alsa-utils/pull/174 Patch URL : https://github.com/alsa-project/alsa-utils/pull/174.patch Repository URL: https://github.com/alsa-project/alsa-utils

1 0

unable to install alsa-utils with newest pulseaudio
by GitHub issues - opened 10 Oct '22

10 Oct '22

alsa-project/alsa-utils issue #173 was opened from voncloft: I installed and upgraded pulse audio to version 16.1 I keep receiving the following error when trying to upgrade alsa-utils (the latest version): `/bin/sh ../libtool --tag=CC --mode=link gcc -Wall -g -D_REENTRANT -D_GNU_SOURCE -g -O2 -module -avoid-version -export-dynamic -no-undefined -Wl,-z,defs -o libasound_module_conf_pulse.la -rpath /usr/lib/alsa-lib conf_pulse.lo -lasound -lpulse -pthread -lasound /bin/grep: /usr/lib/pulseaudio/libpulsecommon-13.0.la: No such file or directory /bin/sed: can't read /usr/lib/pulseaudio/libpulsecommon-13.0.la: No such file or directory libtool: error: '/usr/lib/pulseaudio/libpulsecommon-13.0.la' is not a valid libtool archive make[2]: *** [Makefile:535: libasound_module_conf_pulse.la] Error 1 make[2]: Leaving directory '/sources/alsa-plugins/pulse' make[1]: *** [Makefile:444: all-recursive] Error 1 make[1]: Leaving directory '/sources/alsa-plugins' make: *** [Makefile:376: all] Error 2` What exactly is going on here? Issue URL : https://github.com/alsa-project/alsa-utils/issues/173 Repository URL: https://github.com/alsa-project/alsa-utils

1 0