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

[alsa-devel] Options for u_audio.c behavior when UAC2 host is disconnected/idle
by Pavel Hofman 10 Feb '20

10 Feb '20

Hi, I would like to discuss options to make the g_audio device more usable. Currently if the USB UAC2 function does not supply/consume any audio data (USB disconnected or the host side is not using the UAC2 gadget, the g_audio devices (both capture and playback) are waiting, leading eventually to an error. This makes using the feature rather inconvenient. Possible options (certainly more are available) 1) The alsa devices will be openable at any time and when the UAC2 is not producing/consuming, the alsa devices will be generating zeros/dropping samples. Dropping samples would be similar to the snd-aloop behavior. 2) Opening the alsa devices will fail when the UAC2 is not actively running, and the pcm stream will be closed when UAC2 stops being active. This is similar to how SPDIF receivers are coded in alsa drivers - if change in the incoming SPDIF stream is detected (no samples, different sample rate), the pcm stream is closed https://github.com/torvalds/linux/blob/master/sound/i2c/other/ak4117.c#L504 It is up to the application to handle the error/close. The behavior could be configurable via some params, if needed. Thanks a lot for any suggestions and recommendations. Best regards, Pavel. P.S.: I posted the same message to linux-usb mailing list, with no response. I think this issue is more alsa-related, hence re-posting to alsa-devel. Or should I keep both mailing lists posted? Thanks for understanding.

1 0

[alsa-devel] [PATCH] ALSA: info: remove redundant assignment to variable c
by Colin King 10 Feb '20

10 Feb '20

From: Colin Ian King <colin.king(a)canonical.com> Variable c is being assigned with the value -1 that is never read, it is assigned a new value in a following while-loop. The assignment is redundant and can be removed. Addresses-Coverity: ("Unused value") Signed-off-by: Colin Ian King <colin.king(a)canonical.com> --- sound/core/info.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sound/core/info.c b/sound/core/info.c index ca87ae4c30ba..8c6bc5241df5 100644 --- a/sound/core/info.c +++ b/sound/core/info.c @@ -604,7 +604,7 @@ int snd_info_card_free(struct snd_card *card) */ int snd_info_get_line(struct snd_info_buffer *buffer, char *line, int len) { - int c = -1; + int c; if (snd_BUG_ON(!buffer || !buffer->buffer)) return 1; -- 2.25.0

2 1

[alsa-devel] [PATCH] ALSA: ali5451: remove redundant variable capture_flag
by Colin King 10 Feb '20

10 Feb '20

From: Colin Ian King <colin.king(a)canonical.com> Variable capture_flag is only ever assigned values, it is never read and hence it is redundant. Remove it. Addresses-Coverity ("Unused value") Signed-off-by: Colin Ian King <colin.king(a)canonical.com> --- sound/pci/ali5451/ali5451.c | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/sound/pci/ali5451/ali5451.c b/sound/pci/ali5451/ali5451.c index 4f524a9dbbca..4462375d2d82 100644 --- a/sound/pci/ali5451/ali5451.c +++ b/sound/pci/ali5451/ali5451.c @@ -1070,7 +1070,7 @@ static int snd_ali_trigger(struct snd_pcm_substream *substream, { struct snd_ali *codec = snd_pcm_substream_chip(substream); struct snd_pcm_substream *s; - unsigned int what, whati, capture_flag; + unsigned int what, whati; struct snd_ali_voice *pvoice, *evoice; unsigned int val; int do_start; @@ -1088,7 +1088,7 @@ static int snd_ali_trigger(struct snd_pcm_substream *substream, return -EINVAL; } - what = whati = capture_flag = 0; + what = whati = 0; snd_pcm_group_for_each_entry(s, substream) { if ((struct snd_ali *) snd_pcm_substream_chip(s) == codec) { pvoice = s->runtime->private_data; @@ -1110,8 +1110,6 @@ static int snd_ali_trigger(struct snd_pcm_substream *substream, evoice->running = 0; } snd_pcm_trigger_done(s, substream); - if (pvoice->mode) - capture_flag = 1; } } spin_lock(&codec->reg_lock); -- 2.25.0

2 1

[alsa-devel] [PATCH] ALSA: hda: remove redundant assignment to variable timeout
by Colin King 10 Feb '20

10 Feb '20

From: Colin Ian King <colin.king(a)canonical.com> Variable timeout is being assigned with the value 200 that is never read, it is assigned a new value in a following do-loop. The assignment is redundant and can be removed. Addresses-Coverity: ("Unused value") Signed-off-by: Colin Ian King <colin.king(a)canonical.com> --- sound/pci/hda/hda_controller.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sound/pci/hda/hda_controller.c b/sound/pci/hda/hda_controller.c index 2609e391ce54..9765652a73d7 100644 --- a/sound/pci/hda/hda_controller.c +++ b/sound/pci/hda/hda_controller.c @@ -373,7 +373,7 @@ static int azx_get_sync_time(ktime_t *device, u32 wallclk_ctr, wallclk_cycles; bool direction; u32 dma_select; - u32 timeout = 200; + u32 timeout; u32 retry_count = 0; runtime = substream->runtime; -- 2.25.0

2 1

[alsa-devel] [PATCH] ALSA: hdsp: remove redundant assignment to variable err
by Colin King 10 Feb '20

10 Feb '20

From: Colin Ian King <colin.king(a)canonical.com> Variable err is being assigned with a value that is never read, it is assigned a new value in the next statement. The assignment is redundant and can be removed. Addresses-Coverity: ("Unused value") Signed-off-by: Colin Ian King <colin.king(a)canonical.com> --- sound/pci/rme9652/hdsp.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/sound/pci/rme9652/hdsp.c b/sound/pci/rme9652/hdsp.c index cc06f0a1a7e4..227aece17e39 100644 --- a/sound/pci/rme9652/hdsp.c +++ b/sound/pci/rme9652/hdsp.c @@ -3353,7 +3353,8 @@ snd_hdsp_proc_read(struct snd_info_entry *entry, struct snd_info_buffer *buffer) return; } } else { - int err = -EINVAL; + int err; + err = hdsp_request_fw_loader(hdsp); if (err < 0) { snd_iprintf(buffer, -- 2.25.0

2 1

[alsa-devel] [PATCH 0/4] ALSA: hda/hdmi: Clean up jack handling
by Takashi Iwai 10 Feb '20

10 Feb '20

Hi, this is a series of cleanup of the jack handling in HD-audio HDMI codec driver, which I realized after the recent regression fix. Basically this changes the jack handling from hda_jack to the own jack objects as Intel HDMI did but applying now to all (generic) codecs. It resulted in a good amount of code reduction in the end. As this is no real fixes, and I'd like to rather share the code between 5.5 and 5.6, it's targeted for 5.7. Only lightly tested on Intel and nouveau. Takashi === Takashi Iwai (4): ALSA: hda/hdmi: Reduce hda_jack_tbl lookup at unsol event handling ALSA: hda/hdmi: Don't use standard hda_jack for generic HDMI jacks ALSA: hda/hdmi: Move runtime PM resume into hdmi_present_sense_via_verbs() ALSA: hda/hdmi: Move ELD parse and jack reporting into update_eld() sound/pci/hda/patch_hdmi.c | 313 +++++++++++++-------------------------------- 1 file changed, 90 insertions(+), 223 deletions(-) -- 2.16.4

3 9

[alsa-devel] broadwell-rt286: more conformance and other fixes
by GitHub pull_request - opened 09 Feb '20

09 Feb '20

alsa-project/alsa-ucm-conf pull request #12 was opened from dpward: Remove JackHWMute, because the hardware does not forcibly shut off the internal speakers or microphone when the jack is in use. Set either PlaybackPriority or CapturePriority for each device. For capture devices, the "ADC0 Capture Switch" was never enabled. CaptureMixerElem and CaptureMasterElem were swapped. Correct "Handset" to "Headset". Apply maximum gain to the headset microphone ("AMIC Volume") when in use, based on testing. Signed-off-by: David Ward <david.ward(a)ll.mit.edu> Request URL : https://github.com/alsa-project/alsa-ucm-conf/pull/12 Patch URL : https://github.com/alsa-project/alsa-ucm-conf/pull/12.patch Repository URL: https://github.com/alsa-project/alsa-ucm-conf

1 0

[alsa-devel] [PATCH v2 0/2] Update FE/BE trigger order based on the command
by Ranjani Sridharan 09 Feb '20

09 Feb '20

Currently, the trigger orders SND_SOC_DPCM_TRIGGER_PRE/POST determine the order in which FE DAI and BE DAI are triggered. In the case of SND_SOC_DPCM_TRIGGER_PRE, the FE DAI is triggered before the BE DAI and in the case of SND_SOC_DPCM_TRIGGER_POST, the BE DAI is triggered before the FE DAI. And this order remains the same irrespective of the trigger command. In the case of the SOF driver, during playback, the FW expects the BE DAI to be triggered before the FE DAI during the START trigger. The BE DAI trigger handles the starting of Link DMA and so it must be started before the FE DAI is started to prevent xruns during pause/release. This can be addressed by setting the trigger order for the FE dai link to SND_SOC_DPCM_TRIGGER_POST. But during the STOP trigger, the FW expects the FE DAI to be triggered before the BE DAI. Retaining the same order during the START and STOP commands, results in FW error as the DAI component in the FW is still active. The issue can be fixed by mirroring the trigger order of FE and BE DAI's during the START and STOP trigger. So, with the trigger order set to SND_SOC_DPCM_TRIGGER_PRE, the FE DAI will be trigger first during SNDRV_PCM_TRIGGER_START/STOP/RESUME and the BE DAI will be triggered first during the STOP/SUSPEND/PAUSE commands. Conversely, with the trigger order set to SND_SOC_DPCM_TRIGGER_POST, the BE DAI will be triggered first during the SNDRV_PCM_TRIGGER_START/STOP/RESUME commands and the FE DAI will be triggered first during the SNDRV_PCM_TRIGGER_STOP/SUSPEND/PAUSE commands. The above change has been tested with the Skylake driver on the Kabylake based chromebook and legacy HDA driver on Kabylake based Dell XPS13. It has also been tested on all platforms with SOF CI without any regressions for the past 3 weeks. More details on the issue can be found here: https://github.com/thesofproject/linux/issues/1160 Changes in v2: Fixed comments on function name and consolidating the switch cases. Ranjani Sridharan (2): ASoC: pcm: update FE/BE trigger order based on the command ASoC: SOF: topology: set trigger order for FE DAI link sound/soc/soc-pcm.c | 95 ++++++++++++++++++++++++++++------------ sound/soc/sof/topology.c | 4 ++ 2 files changed, 72 insertions(+), 27 deletions(-) -- 2.17.1

4 7

[alsa-devel] alsa-gobject: fix workflow of Github Actions to clone requested repository
by GitHub pull_request - opened 09 Feb '20

09 Feb '20

alsa-project/alsa-gobject pull request #7 was opened from takaswie: Even if any pull request is triggered, in 'build_in_ubuntu_on_lxd' job of 'Build test' workflow, upstream repository is cloned and requested git hash is checked out. However this fails because the hash is in requested repository. This commit fixes the workflow so that requested repository is cloned. Fixes: 8cb6715aab65 ('Add support workflow of Github Actions') Signed-off-by: Takashi Sakamoto <o-takashi(a)sakamocchi.jp> Request URL : https://github.com/alsa-project/alsa-gobject/pull/7 Patch URL : https://github.com/alsa-project/alsa-gobject/pull/7.patch Repository URL: https://github.com/alsa-project/alsa-gobject

1 0

[alsa-devel] alsa-gobject Add shared library to operate ALSA Timer character device
by GitHub pull_request - opened 09 Feb '20

09 Feb '20

alsa-project/alsa-gobject pull request #6 was opened from takaswie: This request is to add a new library, libalsatimer, to operate ALSA Timer character device. In design of ALSA Timer core, one character device is added to Linux system. Usually a special file, '/dev/snd/timer' is used for the character device. Userspace applications can enumerate actual timer device to operate the character device. For enumerations of the timer devices, the library includes a global functions, 'alsatimer_get_device_id_list()'. The timer devices are identified by 'ALSATimerDeviceId' which is a GObject boxed object to handle 'struct snd_timer_id'. The other global functions are available to the timer device, as a wrapper of some ioctl commands below: * alsatimer_get_device_info() = SNDRV_TIMER_IOCTL_GINFO * alsatimer_get_device_status() = SNDRV_TIMER_IOCTL_GPARAMS * alsatimer_set_device_params() = SNDRV_TIMER_IOCTL_GSTATUS Userspace applications can allocate timer instances and attach them to the timer device to receive timer events. The library includes 'ALSATimerUserInstance' which is an GObject-derived object to maintain file descriptor of ALSA Timer character device. Usually, the series of below calls are expected to use in the order to start emission of timer events: * alsatimer_user_instance_new() * alsatimer_user_instance_open() * alsatimer_user_instance_attach() * alsatimer_user_instance_set_params() * alsatimer_user_instance_start() * alsatimer_user_instance_stop() Against the attachment to timer device, there's a way to associate the instance to the another instance as slave. This is achieved by a call of 'alsatimer_user_instance_attach_as_slave()'. The 'ALSATimerDeviceId' is the lack of properties relevant to slave association since the information relevant to slave association in kernel space is not available for userspace application at all and the properties are just used to transfer the information from userspace by one way. ALSA Timer core supports two types of events, which is switched by 'tread operation'. To handle these two, the library has 'ALSATimerEventData' which is an GObject-derived abstract class. There are two specialized classes from it; 'ALSATimerEventDataTick' and 'ALSATimerEventDataTimestamp'. The former is just for tick event and the latter is for events with its type and timestamp. The selection is done by a call of attach function with the type of event data. Request URL : https://github.com/alsa-project/alsa-gobject/pull/6 Patch URL : https://github.com/alsa-project/alsa-gobject/pull/6.patch Repository URL: https://github.com/alsa-project/alsa-gobject

1 0