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

[PATCH] Docs: hda: Fix spelling mistakes
by huangjianghui 10 Jun '21

10 Jun '21

correct Reatek to Realtek Signed-off-by: huangjianghui <huangjianghui(a)uniontech.com> --- Documentation/sound/hd-audio/controls.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/sound/hd-audio/controls.rst b/Documentation/sound/hd-audio/controls.rst index f2ebc4f79b44..dbe6483f4ff4 100644 --- a/Documentation/sound/hd-audio/controls.rst +++ b/Documentation/sound/hd-audio/controls.rst @@ -102,7 +102,7 @@ Conexant codecs --------------- Auto-Mute Mode - See Reatek codecs. + See Realtek codecs. Analog codecs -- 2.20.1

2 1

[PATCH] sound/arm: Remove unnecessary variables
by zuoqilin1＠163.com 10 Jun '21

10 Jun '21

From: zuoqilin <zuoqilin(a)yulong.com> There is no need to define the variable "ret" to receive. Signed-off-by: zuoqilin <zuoqilin(a)yulong.com> --- sound/arm/pxa2xx-ac97.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/sound/arm/pxa2xx-ac97.c b/sound/arm/pxa2xx-ac97.c index 6322e639..a67e668 100644 --- a/sound/arm/pxa2xx-ac97.c +++ b/sound/arm/pxa2xx-ac97.c @@ -47,9 +47,7 @@ static unsigned short pxa2xx_ac97_legacy_read(struct snd_ac97 *ac97, static void pxa2xx_ac97_legacy_write(struct snd_ac97 *ac97, unsigned short reg, unsigned short val) { - int __always_unused ret; - - ret = pxa2xx_ac97_write(ac97->num, reg, val); + pxa2xx_ac97_write(ac97->num, reg, val); } static const struct snd_ac97_bus_ops pxa2xx_ac97_ops = { -- 1.9.1

2 1

[PATCH v3 0/3] ALSA: pcm: add snd_pcm_period_elapsed() variant without acquiring lock of PCM substream
by Takashi Sakamoto 10 Jun '21

10 Jun '21

Hi, This patchset is revised version of my previous one: * https://lore.kernel.org/alsa-devel/20210609143145.146680-1-o-takashi@sakamo… All of drivers in ALSA firewire stack have two chances to process isochronous packets of any isochronous context; in software IRQ context for 1394 OHCI, and in process context of ALSA PCM application. In the process context, callbacks of .pointer and .ack are utilized. The callbacks are done by ALSA PCM core under acquiring lock of PCM substream, In design of ALSA PCM core, call of snd_pcm_period_elapsed() is used for drivers to awaken user processes from waiting for available frames. The function voluntarily acquires lock of PCM substream, therefore it is not called in the process context since it causes dead lock. As a workaround to avoid the dead lock, all of drivers in ALSA firewire stack use workqueue to delegate the call. This patchset is my attempt for the issue. A variant of 'snd_pcm_period_elapsed()' without lock acquisition is going to be added, named 'snd_pcm_period_elapsed_under_stream_lock()'. The call is available in callbacks of .pointer and .ack of snd_pcm_ops structure. Changes from v2: * delete context section from kernel API documentation Takashi Sakamoto (3): ALSA: pcm: add snd_pcm_period_elapsed() variant without acquiring lock of PCM substream ALSA: firewire-lib: operate for period elapse event in process context ALSA: firewire-lib: obsolete workqueue for period update include/sound/pcm.h | 1 + sound/core/pcm_lib.c | 64 +++++++++++++++++++++++++++-------- sound/firewire/amdtp-stream.c | 46 ++++++++----------------- sound/firewire/amdtp-stream.h | 1 - 4 files changed, 64 insertions(+), 48 deletions(-) -- 2.27.0

2 4

[Bug] Duplication in Array Element not Handled in Parsing conf
by GitHub issues - opened 10 Jun '21

10 Jun '21

alsa-project/alsa-lib issue #151 was opened from aiChaoSONG: When parsing array element in conf files, an auto-increase number is used as config id(`snd_config_t->id`), and array element as the config value(`snd_config_t->u.string/integer/integer64/real`), duplication is not handle in `parse_array_defs/parse_array_def/parse_value` functions. Suppose we have a conf: ``` array [ "a" "b" "a" ] ``` the parsed result will be: ``` parent | ---- snd_config_t {id: "0", u.string: "a"} | ---- snd_config_t {id: "1", u.string: "b"} | ---- snd_config_t {id: "2", u.string: "a"} ``` The duplication in "a" may be desired. But please consider this condition: suppose we have four conf files A, B, C and D, where A is the conf above, let B include A, C include A, D include B and C, so D include A twice indirectly. File A will be processed twice when parsing D, because duplication is not handled, here comes the problem, the parsed result of A in D is: ``` parent | ---- snd_config_t {id: "0", u.string: "a"} | ---- snd_config_t {id: "1", u.string: "b"} | ---- snd_config_t {id: "2", u.string: "a"} | ---- snd_config_t {id: "3", u.string: "a"} | ---- snd_config_t {id: "4", u.string: "b"} | ---- snd_config_t {id: "5", u.string: "a"} ``` This is obviously wrong. I think handle duplication in parse_value is not the solution, because element duplication in an array is wanted. The key problem here is that we parse the same conf more than once. Issue URL : https://github.com/alsa-project/alsa-lib/issues/151 Repository URL: https://github.com/alsa-project/alsa-lib

1 0

[bug report] ASoC: rsnd: add null CLOCKIN support
by Dan Carpenter 10 Jun '21

10 Jun '21

Hello Kuninori Morimoto, The patch d6956a7dde6f: "ASoC: rsnd: add null CLOCKIN support" from May 24, 2021, leads to the following static checker warning: sound/soc/sh/rcar/adg.c:435 rsnd_adg_get_clkin() warn: 'clk' isn't an ERR_PTR sound/soc/sh/rcar/adg.c 423 static int rsnd_adg_get_clkin(struct rsnd_priv *priv) 424 { 425 struct rsnd_adg *adg = priv->adg; 426 struct device *dev = rsnd_priv_to_dev(priv); 427 struct clk *clk; 428 int i; 429 430 for (i = 0; i < CLKMAX; i++) { 431 clk = devm_clk_get(dev, clk_name[i]); If devm_clk_get() returns NULL that's not an error. 432 433 if (IS_ERR(clk)) 434 clk = rsnd_adg_null_clk_get(priv); But I think if rsnd_adg_null_clk_get() returns an error then it is an error. 435 if (IS_ERR(clk)) This is impossible. 436 goto err; So I think it should be: if (IS_ERR(clk)) { clk = rsnd_adg_null_clk_get(priv); if (!clk) goto err; } 437 438 adg->clk[i] = clk; 439 } 440 441 return 0; 442 443 err: 444 dev_err(dev, "adg clock IN get failed\n"); 445 446 rsnd_adg_null_clk_clean(priv); 447 448 return -EIO; 449 } regards, dan carpenter

2 3

[PATCH v3 0/3] ALSA: pcm: add snd_pcm_period_elapsed() variant without acquiring lock of PCM substream
by Takashi Sakamoto 10 Jun '21

10 Jun '21

Hi, This patchset is revised version of my previous one: * https://lore.kernel.org/alsa-devel/20210609143145.146680-1-o-takashi@sakamo… All of drivers in ALSA firewire stack have two chances to process isochronous packets of any isochronous context; in software IRQ context for 1394 OHCI, and in process context of ALSA PCM application. In the process context, callbacks of .pointer and .ack are utilized. The callbacks are done by ALSA PCM core under acquiring lock of PCM substream, In design of ALSA PCM core, call of snd_pcm_period_elapsed() is used for drivers to awaken user processes from waiting for available frames. The function voluntarily acquires lock of PCM substream, therefore it is not called in the process context since it causes dead lock. As a workaround to avoid the dead lock, all of drivers in ALSA firewire stack use workqueue to delegate the call. This patchset is my attempt for the issue. A variant of 'snd_pcm_period_elapsed()' without lock acquisition is going to be added, named 'snd_pcm_period_elapsed_under_stream_lock()'. The call is available in callbacks of .pointer and .ack of snd_pcm_ops structure. Changes from v2: * delete context section from kernel API documentation Takashi Sakamoto (3): ALSA: pcm: add snd_pcm_period_elapsed() variant without acquiring lock of PCM substream ALSA: firewire-lib: operate for period elapse event in process context ALSA: firewire-lib: obsolete workqueue for period update include/sound/pcm.h | 1 + sound/core/pcm_lib.c | 64 +++++++++++++++++++++++++++-------- sound/firewire/amdtp-stream.c | 46 ++++++++----------------- sound/firewire/amdtp-stream.h | 1 - 4 files changed, 64 insertions(+), 48 deletions(-) -- 2.27.0

1 1

aplay change to use 16-bit samples by default is not backwards compatible and is not documented
by GitHub issues - opened 10 Jun '21

10 Jun '21

alsa-project/alsa-utils issue #96 was opened from nwoeanhinnogaehr: The change introduced in https://github.com/alsa-project/alsa-utils/commit/0c5948e98a6a8535c89b7bcab… breaks a lot of scripts and other programs I have which invoke `aplay` and expect the default sample format to be U8. While I think it's somewhat reasonable to make this change given that U8 is a rather low quality sample format, it's worth acknowledging that aplay has had this behavior for a very long time and many people probably don't expect it to change. Given that the commit log seems to only talk about the case of `arecord`, I wonder if we could reach a compromise and keep the format as U8 for `aplay` and switch it for `arecord`, since users are unlikely to complain about poor sound quality when *playing raw audio* (surely they would take the time to get the sample format set up correctly before attempting to play raw audio). Also, the man page has not been updated to reflect this change and still says that U8 is the default. Issue URL : https://github.com/alsa-project/alsa-utils/issues/96 Repository URL: https://github.com/alsa-project/alsa-utils

1 0

[PATCH v2 0/8] ASoC: tidyup snd_soc_of_parse_daifmt()
by Kuninori Morimoto 10 Jun '21

10 Jun '21

Hi Mark These are v2 of parsing for daifmt. I want to add new audio-graph-card2 sound card driver, and this is last part of necessary soc-core cleanup for it. Current some drivers are using DT, and then, snd_soc_of_parse_daifmt() parses daifmt, but bitclock/frame provider parsing part is one of headache, because we are assuming below both cases. A) node { bitclock-master; frame-master; ... }; B) link { bitclock-master = <&xxx>; frame-master = <&xxx>; ... }; The original was style A), and style B) was added later. snd_soc_of_parse_daifmt() parses A) style as original style, and user need to update to B) style for clock_provider part if needed. To handle it more flexibile, this patch-set adds new functions which separates snd_soc_of_parse_daifmt() helper function. snd_soc_daifmt_parse_format() : format part snd_soc_daifmt_parse_clock_provider_as_flag() : clock part for style A) snd_soc_daifmt_parse_clock_provider_as_phandl() : clock part for style B) snd_soc_daifmt_parse_clock_provider_as_bitmap() : clock part use with _from_bitmap v1 -> v2 - tidyup parse_clock_provider functions to _as_flag/phandle/bitmap() - don't exchange code style on each drivers. Link: https://lore.kernel.org/r/875yypdxlm.wl-kuninori.morimoto.gx@renesas.com Kuninori Morimoto (8): ASoC: soc-core: add snd_soc_daifmt_clock_provider_from_bitmap() ASoC: soc-core: add snd_soc_daifmt_clock_provider_fliped() ASoC: soc-core: add snd_soc_daifmt_parse_format/clock_provider() ASoC: atmel: switch to use snd_soc_daifmt_parse_format/clock_provider() ASoC: fsl: switch to use snd_soc_daifmt_parse_format/clock_provider() ASoC: meson: switch to use snd_soc_daifmt_parse_format/clock_provider() ASoC: simple-card-utils: switch to use snd_soc_daifmt_parse_format/clock_provider() ASoC: soc-core: remove snd_soc_of_parse_daifmt() include/sound/soc.h | 21 ++++-- sound/soc/atmel/mikroe-proto.c | 16 +++-- sound/soc/fsl/fsl-asoc-card.c | 14 ++-- sound/soc/generic/simple-card-utils.c | 19 ++--- sound/soc/meson/meson-card-utils.c | 13 ++-- sound/soc/soc-core.c | 99 +++++++++++++++++---------- 6 files changed, 110 insertions(+), 72 deletions(-) -- 2.25.1

2 11

[PATCH 0/5] ALSA: More abstracition of memory alloc helpers
by Takashi Iwai 09 Jun '21

09 Jun '21

Hi, this is a patch set for the code cleanup and refactoring around the ALSA core memory allocation helpers. It begins with a cleanup of the non-used code, then followed by the refacotoring with the new ops, finally moved the memory-specific mmap handling code from PCM to the core memalloc. Takashi === Takashi Iwai (5): ALSA: trident: Drop shadow TLB pointer table ALSA: core: Drop snd_sgbuf_get_ptr() ALSA: core: Abstract memory alloc helpers ALSA: core: Move mmap handler into memalloc ops ALSA: core: Add continuous and vmalloc mmap ops include/sound/memalloc.h | 83 +----- include/sound/pcm.h | 19 -- sound/core/memalloc.c | 444 +++++++++++++++++++---------- sound/core/memalloc_local.h | 19 ++ sound/core/pcm_local.h | 5 - sound/core/pcm_memory.c | 21 -- sound/core/pcm_native.c | 39 +-- sound/core/sgbuf.c | 90 ++++-- sound/pci/trident/trident.h | 1 - sound/pci/trident/trident_main.c | 11 +- sound/pci/trident/trident_memory.c | 53 ++-- 11 files changed, 405 insertions(+), 380 deletions(-) create mode 100644 sound/core/memalloc_local.h -- 2.26.2

1 5

Current version not working with Focusrite Scarlett 18i20
by GitHub issues - opened 09 Jun '21

09 Jun '21

alsa-project/alsa-lib issue #150 was opened from TheBitFighter: Hello, I hope I am in the right repository for this. My arch system updated alsa-card-profiles and alsa-utils today which caused my interface, a Focusrite Scarlett 18i20 1st gen to stop working. The card was still showing up in pulse and showed output, however no sound was actually played. Input was still working fine. It sounded like the output stage of the interface had been disabled, and the problem could only be fixed by booting Windows and setting new routing settings in Scarlett MixControl. The interface had exhibited some resetting and popping behavior for a few versions now (when stopping playback, changing application and playing something else there), but continued to work (given a few instances where sample rate played mismatched sample rate sent which caused weird audio slowdowns). It only stopped working today. What I did initially was reinstall the older versions of these two packages, which did not fix the problem. I now downgraded alsa-libs (1.2.5-2 -> 1.2.4-2), alsa-card-profiles (1:0.3.29-2 -> 1:0.3.28-1), lib32-alsa-lib (1.2.5-2 -> 1.2.4-1), alsa-topology-conf (1.2.5-1 -> 1.2.4-1), and alsa-ucm-conf (1.2.5-1 -> 1.2.4-1) which fixed the problem. (alsa-utils is at 1.2.5-2) `cat /etc/asound/version` now reports `Advanced Linux Sound Architecture Driver Version k5.12.9-arch1-1.` This also fixed the popping/resetting issues I had before. Thanks for the help! If you need any further information I am happy to help. Issue URL : https://github.com/alsa-project/alsa-lib/issues/150 Repository URL: https://github.com/alsa-project/alsa-lib

1 0