Yeah pulseaudio is doing the same on Raspbian with USB devices.
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10
From: alsa-devel-request@alsa-project.orgmailto:alsa-devel-request@alsa-project.org Sent: 09 June 2020 22:40 To: alsa-devel@alsa-project.orgmailto:alsa-devel@alsa-project.org Subject: Alsa-devel Digest, Vol 160, Issue 72
Send Alsa-devel mailing list submissions to alsa-devel@alsa-project.org
To subscribe or unsubscribe via the World Wide Web, visit https://mailman.alsa-project.org/mailman/listinfo/alsa-devel or, via email, send a message with subject or body 'help' to alsa-devel-request@alsa-project.org
You can reach the person managing the list at alsa-devel-owner@alsa-project.org
When replying, please edit your Subject line so it is more specific than "Re: Contents of Alsa-devel digest..."
Today's Topics:
1. Re: [RFC PATCH 0/2] TAS2563 DSP Firmware Loader (Dan Murphy) 2. Re: [RFC PATCH 0/2] TAS2563 DSP Firmware Loader (Mark Brown) 3. Re: [RFC PATCH 1/2] dt-bindings: tas2562: Add firmware support for tas2563 (Mark Brown) 4. Re: [RFC PATCH 1/2] dt-bindings: tas2562: Add firmware support for tas2563 (Dan Murphy) 5. We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail. Jun 09 14:31:33 elrond pulseaudio[11933]: Most likely this is a bug in the ALSA driver 'snd_usb_audio'. Please report this issue to the ALSA developers. Jun 09 14:31:33 elrond pulseaudio[11933]: ALSA woke us up to write new data to the device, but there was actually nothing to write. (GitHub issues - opened) 6. We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail. Jun 09 14:31:33 elrond pulseaudio[11933]: Most likely this is a bug in the ALSA driver 'snd_usb_audio'. Please report this issue to the ALSA developers. Jun 09 14:31:33 elrond pulseaudio[11933]: ALSA woke us up to write new data to the device, but there was actually nothing to write. (GitHub issues - edited) 7. ALSA journalctl error. (GitHub issues - edited) 8. ALSA journalctl Error (GitHub issues - edited)
----------------------------------------------------------------------
Message: 1 Date: Tue, 9 Jun 2020 13:07:50 -0500 From: Dan Murphy dmurphy@ti.com To: Mark Brown broonie@kernel.org Cc: robh@kernel.org, alsa-devel@alsa-project.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, tiwai@suse.com, lgirdwood@gmail.com Subject: Re: [RFC PATCH 0/2] TAS2563 DSP Firmware Loader Message-ID: 6d6aaed3-dac8-e1ec-436c-9b04273df2b3@ti.com Content-Type: text/plain; charset="windows-1252"; format=flowed
Mark
On 6/9/20 12:52 PM, Mark Brown wrote:
On Tue, Jun 09, 2020 at 12:28:39PM -0500, Dan Murphy wrote:
These programs and configurations are selectable via files under the I2C dev node. There may be a better way to select this through ALSA controls but I was unable to find a good example of this. This is why this is an RFC patchset.
I think you can just use enums for most of this - what you want to do I think is parse the firmware, build templates for the controls and then add them with snd_soc_add_component_controls(). Userspace *should* cope with controls being hotplugged.
Yes this was my concern if userspace could cope with dynamic controls.
Dan
------------------------------
Message: 2 Date: Tue, 9 Jun 2020 19:16:15 +0100 From: Mark Brown broonie@kernel.org To: Dan Murphy dmurphy@ti.com Cc: robh@kernel.org, alsa-devel@alsa-project.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, tiwai@suse.com, lgirdwood@gmail.com Subject: Re: [RFC PATCH 0/2] TAS2563 DSP Firmware Loader Message-ID: 20200609181615.GR4583@sirena.org.uk Content-Type: text/plain; charset="us-ascii"
On Tue, Jun 09, 2020 at 01:07:50PM -0500, Dan Murphy wrote:
On 6/9/20 12:52 PM, Mark Brown wrote:
I think you can just use enums for most of this - what you want to do I think is parse the firmware, build templates for the controls and then add them with snd_soc_add_component_controls(). Userspace *should* cope with controls being hotplugged.
Yes this was my concern if userspace could cope with dynamic controls.
Things like alsactl definitely do, and obviously anything that starts after the firmware loads will be fine too.