[pulseaudio-discuss] ALSA with UCM, localized names, nice icons and form factor
Hi, over the past few days, I have been working on integrating the Chromebook 13 CB5-311 from Acer with userspace ALSA and Pulseaudio. Support for it using the alsa-mixer module is far from perfect, so I decided to go with ALSA UCM instead. There are a few things that I currently can't get working with alsa-ucm as well as alsa-mixer. First, the device names are taken as provided from the UCM config and are not localized. alsa-mixer.c's path_verify and option_verify functions provide description maps that lead to using localized names for devices, which is much nicer for users. I would like to have a similar feature for UCM. Can anyone suggest a proper way to do this? Also, alsa-mixer's configuration will provide a device.icon_name that is appropriate for each type of device, which results in such nice icons being displayed in e.g. GNOME's sound control settings. There is no mechanism in place to have something equivalent with UCM. Can anyone suggest a proper way to get this going? Similarly, there is no way to report the form factor of a device, which is used by e.g. GNOME-Shell volume control[0] in the tray. It falls back to matching a "headphone" string to decide whether to go with a headphones or speaker icon. Note that there is no better way to do this in alsa-mixer and the only form factors reported currently come from the udev module, that gets the info from udev matching USB/PCI/etc device strings. Cheers! [0]: https://git.gnome.org/browse/gnome-shell/tree/js/ui/status/volume.js#n171 -- Paul Kocialkowski, developer of low-level free software for embedded devices Website: https://www.paulk.fr/ Coding blog: https://code.paulk.fr/ Git repositories: https://git.paulk.fr/ https://git.code.paulk.fr/ signature.asc Description: This is a digitally signed message part ___ pulseaudio-discuss mailing list pulseaudio-discuss@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
[pulseaudio-discuss] Alsa with UCM, input device-based jack detection
Hi, I'm trying to get Jack detection with ALSA UCM working nicely on an ARM platform but I am currently hitting a few issues. In the kernel, soc-jack (used on e.g. ARM SoCs) will not create a kcontrol so the JackControl property can't be used directly (as far as I have understood). Some UCM files provide "JackName" to specify the input device name to use, which is provided in the ASoC case. Would it make sense to add support for JackName in ALSA? (Even though I understood it is somewhat deprecated and using input devices may lead to right issues.) However, plug-in/out events can lead to some controls to be toggled by the kernel driver. Would it make sense, would it work and would it be a good idea to use them for the "JackControl" property? What do you think is the proper solution here? Thanks [0]: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/sound/soc/soc-jack.c?id=refs/tags/v4.8-rc7#n51 -- Paul Kocialkowski, developer of low-level free software for embedded devices Website: https://www.paulk.fr/ Coding blog: https://code.paulk.fr/ Git repositories: https://git.paulk.fr/ https://git.code.paulk.fr/ signature.asc Description: This is a digitally signed message part ___ pulseaudio-discuss mailing list pulseaudio-discuss@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
[pulseaudio-discuss] Master is frozen
Hi, The master branch is frozen as of today. The first 10.0 release candidate will be released once the release blocker bugs are fixed. We have six blockers open. Four of them have fixes submitted, pending review. The remaining two blockers without a fix are: 97769 - memfd doesn't work between 64-bit server and 32-bit client https://bugs.freedesktop.org/show_bug.cgi?id=97769 Ahmed Darwish said he'd work on this. 95352 - PA crash on Assertion 'pa_atomic_load(>pool->stat.n_imported) > 0 https://bugs.freedesktop.org/show_bug.cgi?id=95352 I'll try to fix this. I expect the fix to be pretty invasive, however, so it may be best to remove the blocker status from this. The bug isn't a regression, so I think it's ok to postpone the fix until 11.0. -- Tanu ___ pulseaudio-discuss mailing list pulseaudio-discuss@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
