public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Chancel Liu <chancel.liu@nxp.com>
Cc: perex@perex.cz, tiwai@suse.com, ivan.orlov0322@gmail.com,
	linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: aloop: Introduce a function to get if access is interleaved mode
Date: Fri, 12 Jan 2024 09:46:17 +0100	[thread overview]
Message-ID: <87bk9rndly.wl-tiwai@suse.de> (raw)
In-Reply-To: <20240111025219.2678764-1-chancel.liu@nxp.com>

On Thu, 11 Jan 2024 03:52:19 +0100,
Chancel Liu wrote:
> 
> There's a use case that playback stream of a loopback cable works on
> RW_INTERLEAVED mode while capture stream works on MMAP_INTERLEAVED mode:
> 
> aplay -Dhw:Loopback,0,0 S32_48K_2ch.wav;
> arecord -Dplughw:Loopback,1,0 -fS32_LE -r16000 -c2 cap.wav;
> 
> The plug plugin handles only slave PCM support MMAP mode. Not only plug
> plugin but also other plugins like direct plugins(dmix/dsnoop/dshare)
> work on MMAP access mode. In this case capture stream is the slave
> PCM works on MMAP_INTERLEAVED mode. However loopback_check_format()
> rejects this access setting and return:
> 
> arecord: pcm_read:2240: read error: Input/output error
> 
> To fix it a function called is_access_interleaved() is introduced to
> get if access is interleaved mode. If both access of capture stream and
> playback stream is interleaved mode loopback_check_format() will allow
> this kind of access setting.
> 
> Fixes: 462494565c27 ("ALSA: aloop: Add support for the non-interleaved access mode")
> Signed-off-by: Chancel Liu <chancel.liu@nxp.com>

Applied now.  Thanks.


Takashi

      reply	other threads:[~2024-01-12  8:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-11  2:52 [PATCH] ALSA: aloop: Introduce a function to get if access is interleaved mode Chancel Liu
2024-01-12  8:46 ` Takashi Iwai [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87bk9rndly.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=chancel.liu@nxp.com \
    --cc=ivan.orlov0322@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox