mirror of
https://github.com/nxp-imx/linux-imx.git
synced 2025-07-08 18:35:20 +02:00
ALSA: timer: Relax start tick time check for slave timer elements
commitccbfcac058
upstream. The recent addition of a sanity check for a too low start tick time seems breaking some applications that uses aloop with a certain slave timer setup. They may have the initial resolution 0, hence it's treated as if it were a too low value. Relax and skip the check for the slave timer instance for addressing the regression. Fixes:4a63bd179f
("ALSA: timer: Set lower bound of start tick time") Cc: <stable@vger.kernel.org> Link: https://github.com/raspberrypi/linux/issues/6294 Link: https://patch.msgid.link/20240810084833.10939-1-tiwai@suse.de Signed-off-by: Takashi Iwai <tiwai@suse.de> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
This commit is contained in:
parent
1f3b52c0fd
commit
bb121128fd
|
@ -556,7 +556,7 @@ static int snd_timer_start1(struct snd_timer_instance *timeri,
|
||||||
/* check the actual time for the start tick;
|
/* check the actual time for the start tick;
|
||||||
* bail out as error if it's way too low (< 100us)
|
* bail out as error if it's way too low (< 100us)
|
||||||
*/
|
*/
|
||||||
if (start) {
|
if (start && !(timer->hw.flags & SNDRV_TIMER_HW_SLAVE)) {
|
||||||
if ((u64)snd_timer_hw_resolution(timer) * ticks < 100000) {
|
if ((u64)snd_timer_hw_resolution(timer) * ticks < 100000) {
|
||||||
result = -EINVAL;
|
result = -EINVAL;
|
||||||
goto unlock;
|
goto unlock;
|
||||||
|
|
Loading…
Reference in New Issue
Block a user