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

[alsa-devel] [PATCH v8 0/6] drm/bridge: sii902x: HDMI-audio support and some fixes
by Jyri Sarha 31 May '19

31 May '19

I think these should be ready for applying to drm-misc. Changes since v7: - Debased on top of the lasts drm-misc-next and tested - "dt-bindings: display: sii902x: Add HDMI audio bindings" - Dropped off "or higher to avoid conflict with video ports" and added "Reviewed-by: Rob Herring <robh(a)kernel.org>" Ther previous round: https://patchwork.kernel.org/cover/10919173/ Jyri Sarha (5): drm/bridge: sii902x: Set output mode to HDMI or DVI according to EDID drm/bridge: sii902x: pixel clock unit is 10kHz instead of 1kHz dt-bindings: display: sii902x: Remove trailing white space dt-bindings: display: sii902x: Add HDMI audio bindings drm/bridge: sii902x: Implement HDMI audio support Tomi Valkeinen (1): drm/bridge: sii902x: add input_bus_flags .../bindings/display/bridge/sii902x.txt | 42 +- drivers/gpu/drm/bridge/sii902x.c | 488 +++++++++++++++++- 2 files changed, 522 insertions(+), 8 deletions(-) -- Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki

2 7

[alsa-devel] [BISECT] No audio after "ASoC: core: use component driver name as component name"
by Krzysztof Kozlowski 31 May '19

31 May '19

Hi, Bisect points to commit b19671d6caf1ac393681864d5d85dda9fa99a448 Author: Tzung-Bi Shih <tzungbi(a)google.com> Date: Wed May 29 14:22:14 2019 +0800 ASoC: core: use component driver name as component name as a reason of failure of missing Audio card on Odroid XU3 board (ARMv7, Exynos5422, max98090 codec). Full kernel log: https://krzk.eu/#/builders/1/builds/3349/steps/14/logs/serial0 The problem might be in component name. The driver->name and fmt_single_name(dev, &component->id) are: snd_dmaengine_pcm != 3830000.i2s snd_dmaengine_pcm != 3830000.i2s-sec samsung-i2s != 3830000.i2s This commit should not go in without fixing the users of old behavior... I could adjust the platform names for primary and secondary links... but now it looks like two components will have the same name. Best regards, Krzysztof

3 2

[alsa-devel] aplay - pcm_read: Input/output error
by GitHub issues - edited 31 May '19

31 May '19

alsa-project/alsa-lib issue #7 was edited from mrajwa: Hello, I came across an issue with custom built aplay (system one works OK on Ubuntu 18.04): I have fetched both alsa-lib and alsa-utils repositories, built them now try to run: `path_to_aplay/aplay -C -D hw:0,8 -r 16000 -f S16_LE -c 2 tmp.wav -vvv` Immediately after the start it prints hw params and the error message saying: `arecord: pcm_read:2103: read errorL Input/output error` As I said system aplay works fine. Moreover I compared hw params for both system and this custom built aplay and they are exactly the same! I also tried to built alsa-utils from debian package here I did: `apt source alsa-lib && sudo apt build-dep alsa-utils && fakeroot debian/rules clean && fakeroot debian/rules build && fakeroot debian/rules binary` All finished fine, now I repeated above steps for alsa-utils and here is a problem at `fakeroot debian/rules binary` step. At some point it stops with an error message saying: `dpkg-shlibdeps: error: no dependency information found for /usr/lib/libasound.co.s2 (used by debian/alsa-utils/usr/bin/alsaucm)` Does anybody have any idea what is going on here? Issue URL : https://github.com/alsa-project/alsa-lib/issues/7 Repository URL: https://github.com/alsa-project/alsa-lib

1 0

[alsa-devel] aplay - pcm_read: Input/output error
by GitHub issues - edited 31 May '19

31 May '19

alsa-project/alsa-lib issue #7 was edited from mrajwa: Hello, I came across an issue with custom built aplay (system one works OK on Ubuntu 18.04): I have fetched both alsa-lib and alsa-utils repositories, built them now try to run: `path_to_aplay/aplay -C -D hw:0,8 -r 16000 -f S16_LE -c 2 tmp.wav -vvv` Immediately after the start it prints hw params and the error message saying: `arecord: pcm_read:2103: read errorL Input/output error` As I said system aplay works fine. Moreover I compared hw params for both system and this custom built aplay and they are exactly the same! I also tried to built alsa-utils from debian package here I did: apt source alsa-lib && sudo apt build-dep alsa-utils && fakeroot debian/rules clean && fakeroot debian/rules build && fakeroot debian/rules binary All finished fine, now I repeated above steps for alsa-utils and here is aproblem at fakeroot debian/rules binary step. At some point it stops with error message saying: `dpkg-shlibdeps: error: no dependency information found for /usr/lib/libasound.co.s2 (used by debian/alsa-utils/usr/bin/alsaucm)` Does anybody have any idea what is going on here? Issue URL : https://github.com/alsa-project/alsa-lib/issues/7 Repository URL: https://github.com/alsa-project/alsa-lib

1 0

[alsa-devel] aplay - pcm_read: Input/output error
by GitHub issues - opened 31 May '19

31 May '19

alsa-project/alsa-lib issue #7 was opened from mrajwa: Hello, I came across an issue with custom built aplay (system one works OK on Ubuntu 18.04): I have fetched both alsa-lib and alsa-utils repositories, built them now try to run: `path_to_aplay/aplay -C -D hw:0,8 -r 16000 -f S16_LE -c 2 tmp.wav -vvv` Immediately after the start it prints hw_params and the and error message saying: `arecord: pcm_read:2103: read errorL Input/output error` As I said system aplay works fine. Moreover I compared hw_params for both system and this custom built aplay and they are exactly the same! I also tried to built alsa-utils from debian package here I did: apt source alsa-lib && sudo apt build-dep alsa-utils && fakeroot debian/rules clean && fakeroot debian/rules build && fakeroot debian/rules binary All finished fine, now I repeated above steps for alsa-utils and here is aproblem at fakeroot debian/rules binary step. At some point it stops with error message saying: `dpkg-shlibdeps: error: no dependency information found for /usr/lib/libasound.co.s2 (used by debian/alsa-utils/usr/bin/alsaucm)` Does anybody have any idea what is going on here? Issue URL : https://github.com/alsa-project/alsa-lib/issues/7 Repository URL: https://github.com/alsa-project/alsa-lib

1 0

[alsa-devel] [PATCH] Revert "ASoC: core: use component driver name as component name"
by Krzysztof Kozlowski 31 May '19

31 May '19

Using component driver as a name is not unique and it breaks audio in certain configurations, e.g. Hardkernel Odroid XU3 board where following components are registered: - 3830000.i2s with driver snd_dmaengine_pcm - 3830000.i2s-sec with driver snd_dmaengine_pcm - 3830000.i2s with driver 3830000.i2s-sec This reverts commit b19671d6caf1ac393681864d5d85dda9fa99a448. Signed-off-by: Krzysztof Kozlowski <krzk(a)kernel.org> --- sound/soc/soc-core.c | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/sound/soc/soc-core.c b/sound/soc/soc-core.c index 2d3520fca613..7abb017a83f3 100644 --- a/sound/soc/soc-core.c +++ b/sound/soc/soc-core.c @@ -3113,10 +3113,7 @@ static int snd_soc_component_initialize(struct snd_soc_component *component, { struct snd_soc_dapm_context *dapm; - if (driver->name) - component->name = kstrdup(driver->name, GFP_KERNEL); - else - component->name = fmt_single_name(dev, &component->id); + component->name = fmt_single_name(dev, &component->id); if (!component->name) { dev_err(dev, "ASoC: Failed to allocate name\n"); return -ENOMEM; -- 2.7.4

1 0

[alsa-devel] [PATCH 0/3] ALSA: trivial conversions to struct_size()
by Takashi Iwai 31 May '19

31 May '19

Hi, there are a few more places that can be better written with struct_size() macro. Let's replace them. Takashi === Takashi Iwai (3): ALSA: control: Use struct_size() ALSA: hda: Use struct_size() ALSA: hda/ca0132: Use struct_size() sound/core/control.c | 6 +----- sound/pci/hda/hda_codec.c | 2 +- sound/pci/hda/patch_ca0132.c | 2 +- 3 files changed, 3 insertions(+), 7 deletions(-) -- 2.16.4

1 3

[alsa-devel] ALC256 headset mode update
by Kailang 31 May '19

31 May '19

Hi Takashi, Since ALC256 was used for many machines. So, update ALC256 headset mode for separate with ALC255. Many Thanks. BR, Kailang

2 1

[alsa-devel] Fwd: Problem with aplay params
by Martin R 31 May '19

31 May '19

Hello, I have built aplay using github repository https://github.com/alsa-project/alsa-utils/ as well as https://github.com/thesofproject/alsa-lib. Now when I try to run it by "./path_to_aplay/aplay -C -D hw:0,8 -r 16000 -f S16_LE -c 2 tmp.wav -vvv I get immediate error message saying: arecord: pcm_read:2150 read error: Input/output error. Why is it failing? The system aplay/arecord works OK - only the one I built fails with above error. PS: system aplay version is 1.1.8 while the one built by me is 1.19 Regards, Marcin

1 0

[alsa-devel] Question about dapm setup
by Kuninori Morimoto 31 May '19

31 May '19

Hi ALSA ML snd_soc_instantiate_card() setups dapm, but its timing seems very randomly for me. In my understanding, dapm setup timing is not so serious. So, I think we can do it in one place, but are there some reasons ? For example, "xxxx should be called after yyyy" static int snd_soc_instantiate_card(struct snd_soc_card *card) { ... => snd_soc_dapm_debugfs_init(&card->dapm, card->debugfs_card_root); ... if (card->dapm_widgets) snd_soc_dapm_new_controls(&card->dapm, card->dapm_widgets, card->num_dapm_widgets); if (card->of_dapm_widgets) snd_soc_dapm_new_controls(&card->dapm, card->of_dapm_widgets, card->num_of_dapm_widgets); ... snd_soc_dapm_link_dai_widgets(card); snd_soc_dapm_connect_dai_link_widgets(card); if (card->controls) snd_soc_add_card_controls(card, card->controls, card->num_controls); if (card->dapm_routes) snd_soc_dapm_add_routes(&card->dapm, card->dapm_routes, card->num_dapm_routes); if (card->of_dapm_routes) snd_soc_dapm_add_routes(&card->dapm, card->of_dapm_routes, card->num_of_dapm_routes); ... snd_soc_dapm_new_widgets(card); ... dapm_mark_endpoints_dirty(card); snd_soc_dapm_sync(&card->dapm); ... } Thank you for your help !! Best regards --- Kuninori Morimoto

2 4