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

[PATCH v1 0/2] ASoC: codecs: add ES8389 codec driver
by Zhang Yi 03 Mar '25

03 Mar '25

The driver is for codec ES8389 of everest-semi. Zhang Yi (2): ASoC: codecs: add support for ES8389 ASoC: dt-bindings: Add Everest ES8389 audio CODEC .../bindings/sound/everest,es8389.yaml | 98 ++ sound/soc/codecs/Kconfig | 6 +- sound/soc/codecs/Makefile | 2 + sound/soc/codecs/es8389.c | 985 ++++++++++++++++++ sound/soc/codecs/es8389.h | 139 +++ 5 files changed, 1229 insertions(+), 1 deletion(-) create mode 100755 Documentation/devicetree/bindings/sound/everest,es8389.yaml create mode 100644 sound/soc/codecs/es8389.c create mode 100644 sound/soc/codecs/es8389.h -- 2.17.1

3 4

RE: [PATCH v1 2/2] ASoC: dt-bindings: Add Everest ES8389 audio CODEC
by Zhang Yi 03 Mar '25

03 Mar '25

> > + everest,adc-slot: > > + $ref: /schemas/types.yaml#/definitions/uint8 > > + description: | > > + This property is used to set the slots of recording data when multiple > > + codecs are connected in PTDM mode. > > + please set this property to default if you are setting STDM mode. > > + minimum: 0x00 > > + maximum: 0x07 > > + default: 0x00 > > + > > + everest,dac-slot: > > + $ref: /schemas/types.yaml#/definitions/uint8 > > + description: | > > + This property is used to set the slots of playing data when multiple > > + codecs are connected in TDM mode. > > + please do not set this property if you use single codec. > > + minimum: 0x00 > > + maximum: 0x07 > > + default: 0x00 > > Can't the dai-tdm-* properties work for you? We will register multiple codecs inside a single dai_link and differentiate these codecs by of_node. so we can't use dai-tdm-slot* to define the slot for each codec > > + > > + prefix_name: > > + $ref: /schemas/types.yaml#/definitions/string > > + description: device name prefix > > Why do you need this? When using multiple codecs, we utilize prefix_name to distinguish the dapm and kcontro of each individual codec.

1 0

Turn on LED function
by Kailang 03 Mar '25

03 Mar '25

Hi Takashi, Support Mic Mute LED for Lenovo ThinkCentre M series. BR, Kailang

2 1

Fine-grained control bar
by GitHub issues - opened 02 Mar '25

02 Mar '25

alsa-project/alsa-utils issue #295 was opened from egmontkob: The control bars of `alsamixer` are quite coarse. They jump by whole character cells. Often a notable amount of increase or decrease (pressing the Up or Down arrow) isn't reflected visually. I'd like to ask for an opion for more fine-grained looking control bars. If the terminal's / locale's claimed charset, as reported by `nl_langinfo(CODESET)`, is "UTF-8" (as it should be pretty much everywhere nowadays), you could use the Unicode characters [U+2581 to U+2588](https://www.unicode.org/charts/PDF/U2580.pdf) for this purpose. They jump by eighths of a cell's hight. Their foreground color would be the desired bar color (red/white/green) and their background would be the default (or black for `-B`). For consistency, this mode should probably replace the current checkerboard (ACS_CKBOARD) characters by the full block U+2588 and only set its foreground, but maybe this doesn't matter. There are several terminal emulators out there (at least VTE-based ones such as GNOME Terminal and many others; Konsole; and presumably much more) that don't take these glyphs from the font but rather draw them manually to perfectly align them at cell boundaries. In these terminals the bar would look perfectly. In other terminals there might be some ugly gaps at cell boundaries (subject to the selected font), but some people might still prefer this tiny visual glitch over the current coarseness of the bar (again: this would be an option, not a forced new behavior). Thanks for considering this feature request! Issue URL : https://github.com/alsa-project/alsa-utils/issues/295 Repository URL: https://github.com/alsa-project/alsa-utils

1 0

amixer.1: Some remarks and a patch with editorial changes for this man page
by Bjarni Ingi Gislason 01 Mar '25

01 Mar '25

Package: alsa-utils Version: 1.2.13-1 Severity: minor Tags: patch * What led up to the situation? Checking for defects with a new version test-[g|n]roff -mandoc -t -K utf8 -rF0 -rHY=0 -rCHECKSTYLE=10 -ww -z < "man page" [Use "groff -e ' $' -e '\\~$' <file>" to find obvious trailing spaces.] ["test-groff" is a script in the repository for "groff"; is not shipped] (local copy and "troff" slightly changed by me). [The fate of "test-nroff" was decided in groff bug #55941.] * What was the outcome of this action? an.tmac:<stdin>:1: style: .TH missing fourth argument; consider package/project name and version (e.g., "groff 1.23.0") troff:<stdin>:124: warning: trailing space in the line troff:<stdin>:133: warning: trailing space in the line troff:<stdin>:138: warning: trailing space in the line * What outcome did you expect instead? No output (no warnings). -.- General remarks and further material, if a diff-file exist, are in the attachments. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.12.12-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: sysvinit (via /sbin/init) Versions of packages alsa-utils depends on: ii kmod 33+20240816-2 ii libasound2t64 1.2.13-1+b1 ii libatopology2t64 1.2.13-1+b1 ii libc6 2.40-7 ii libfftw3-single3 3.3.10-2+b1 ii libncursesw6 6.5+20250216-1 ii libsamplerate0 0.2.2-4+b2 ii libtinfo6 6.5+20250216-1 alsa-utils recommends no packages. Versions of packages alsa-utils suggests: pn dialog <none> -- no debconf information

1 0

alsaucm.1: Some remarks and a patch with editorial changes for this man page
by Bjarni Ingi Gislason 01 Mar '25

01 Mar '25

Package: alsa-utils Version: 1.2.13-1 Severity: minor Tags: patch * What led up to the situation? Checking for defects with a new version test-[g|n]roff -mandoc -t -K utf8 -rF0 -rHY=0 -rCHECKSTYLE=10 -ww -z < "man page" [Use "groff -e ' $' -e '\\~$' <file>" to find obvious trailing spaces.] ["test-groff" is a script in the repository for "groff"; is not shipped] (local copy and "troff" slightly changed by me). [The fate of "test-nroff" was decided in groff bug #55941.] * What was the outcome of this action? an.tmac:<stdin>:30: style: .TH missing fourth argument; consider package/project name and version (e.g., "groff 1.23.0") * What outcome did you expect instead? No output (no warnings). -.- General remarks and further material, if a diff-file exist, are in the attachments. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.12.12-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: sysvinit (via /sbin/init) Versions of packages alsa-utils depends on: ii kmod 33+20240816-2 ii libasound2t64 1.2.13-1+b1 ii libatopology2t64 1.2.13-1+b1 ii libc6 2.40-7 ii libfftw3-single3 3.3.10-2+b1 ii libncursesw6 6.5+20250216-1 ii libsamplerate0 0.2.2-4+b2 ii libtinfo6 6.5+20250216-1 alsa-utils recommends no packages. Versions of packages alsa-utils suggests: pn dialog <none> -- no debconf information

1 0

unclear example how to use remap plugin
by GitHub issues - opened 01 Mar '25

01 Mar '25

alsa-project/alsa-lib issue #441 was opened from dibalavs: Hello. I combiled 3 sound cards into one vrurtual 5.1 card for PCM, and now trying to make volume control also to use single virtual device, to set up volume for all chanel of virtual 5.1 card. I am trying to use remap control plugin mentioned at [source](https://github.com/alsa-project/alsa-lib/blob/master/src/control/co… But I unable to understand what does it mean: ``` ctl.name { type remap # Remap controls child STR # Child name # or child { # Child definition type STR ... } remap { # the ID strings are parsed in the amixer style like 'name="Headphone Playback Switch",index=2' SRC_ID1_STR DST_ID1_STR SRC_ID2_STR DST_ID2_STR ... } map { # join two stereo controls to one CREATE_ID1_STR { SRC_ID1_STR { vindex.0 0 # source channel 0 to merged channel 0 vindex.1 1 } SRC_ID2_STR { vindex.2 0 vindex.3 1 # source channel 1 to merged channel 3 } } # split stereo to mono CREATE_ID2_STR { SRC_ID3_STR { vindex.0 0 # stereo to mono (first channel) } } CREATE_ID3_STR { SRC_ID4_STR { vindex.0 1 # stereo to mono (second channel) } } } } ``` I do not understand what should I write as SRC and DST?: ``` # the ID strings are parsed in the amixer style like 'name="Headphone Playback Switch",index=2' SRC_ID1_STR DST_ID1_STR SRC_ID2_STR DST_ID2_STR ``` Can you give real example without placeholders like: "name", "SRC", "DST", "STR" ? Issue URL : https://github.com/alsa-project/alsa-lib/issues/441 Repository URL: https://github.com/alsa-project/alsa-lib

1 0

alsatplg.1: Some remarks and a patch with editorial changes for this man page
by Bjarni Ingi Gislason 01 Mar '25

01 Mar '25

Package: alsa-utils Version: 1.2.13-1 Severity: minor Tags: patch * What led up to the situation? Checking for defects with a new version test-[g|n]roff -mandoc -t -K utf8 -rF0 -rHY=0 -rCHECKSTYLE=10 -ww -z < "man page" [Use "groff -e ' $' -e '\\~$' <file>" to find obvious trailing spaces.] ["test-groff" is a script in the repository for "groff"; is not shipped] (local copy and "troff" slightly changed by me). [The fate of "test-nroff" was decided in groff bug #55941.] * What was the outcome of this action? an.tmac:<stdin>:30: style: .TH missing fourth argument; consider package/project name and version (e.g., "groff 1.23.0") an.tmac:<stdin>:108: style: 1 leading space(s) on input line troff:<stdin>:108: warning: trailing space in the line troff:<stdin>:112: warning: trailing space in the line * What outcome did you expect instead? No output (no warnings). -.- General remarks and further material, if a diff-file exist, are in the attachments. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.12.12-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: sysvinit (via /sbin/init) Versions of packages alsa-utils depends on: ii kmod 33+20240816-2 ii libasound2t64 1.2.13-1+b1 ii libatopology2t64 1.2.13-1+b1 ii libc6 2.40-7 ii libfftw3-single3 3.3.10-2+b1 ii libncursesw6 6.5+20250216-1 ii libsamplerate0 0.2.2-4+b2 ii libtinfo6 6.5+20250216-1 alsa-utils recommends no packages. Versions of packages alsa-utils suggests: pn dialog <none> -- no debconf information

1 0

Build with gettext-0.24 intermittently fails
by GitHub issues - edited 28 Feb '25

28 Feb '25

alsa-project/alsa-utils issue #294 was edited from heitbaum: After Autoconf the errors are as follows. The Makefile is not honouring / passing the builddir through. This is a build being done in a subdirectory. ``` Making all in po make[2]: Entering directory '/build/build.LibreELEC-Generic.x86_64-13.0-devel/build/alsa-utils-1.2.13/.x86_64-libreelec-linux-gnu/po' make[2]: *** No rule to make target '/config.status', needed by 'Makefile'. Stop. make[2]: Leaving directory '/build/build.LibreELEC-Generic.x86_64-13.0-devel/build/alsa-utils-1.2.13/.x86_64-libreelec-linux-gnu/po' make[1]: *** [Makefile:471: all-recursive] Error 1 make[1]: Leaving directory '/build/build.LibreELEC-Generic.x86_64-13.0-devel/build/alsa-utils-1.2.13/.x86_64-libreelec-linux-gnu' ``` - This is occurring just like https://github.com/zapping-vbi/zvbi/issues/57 - now testing to see if the change to `AM_GNU_GETTEXT_VERSION([0.24])` fixes the issue Issue URL : https://github.com/alsa-project/alsa-utils/issues/294 Repository URL: https://github.com/alsa-project/alsa-utils

1 0

Build with gettext-0.24 intermittently fails
by GitHub issues - opened 28 Feb '25

28 Feb '25

alsa-project/alsa-utils issue #294 was opened from heitbaum: After Autoconf the errors are as follows. The Makefile is not honouring / passing the builddir through. This is a build being done in a subdirectory. ``` Making all in po make[2]: Entering directory '/build/build.LibreELEC-Generic.x86_64-13.0-devel/build/alsa-utils-1.2.13/.x86_64-libreelec-linux-gnu/po' make[2]: *** No rule to make target '/config.status', needed by 'Makefile'. Stop. make[2]: Leaving directory '/build/build.LibreELEC-Generic.x86_64-13.0-devel/build/alsa-utils-1.2.13/.x86_64-libreelec-linux-gnu/po' make[1]: *** [Makefile:471: all-recursive] Error 1 make[1]: Leaving directory '/build/build.LibreELEC-Generic.x86_64-13.0-devel/build/alsa-utils-1.2.13/.x86_64-libreelec-linux-gnu' ``` Issue URL : https://github.com/alsa-project/alsa-utils/issues/294 Repository URL: https://github.com/alsa-project/alsa-utils

1 0