From: Stephan Gerhold <stephan@gerhold.net>
To: Sameer Pujar <spujar@nvidia.com>
Cc: linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
broonie@kernel.org, tiwai@suse.com
Subject: Re: [alsa-devel] [RFC] ASoC: soc-pcm: crash in snd_soc_dapm_new_dai
Date: Mon, 17 Feb 2020 15:41:20 +0100 [thread overview]
Message-ID: <20200217144120.GA243254@gerhold.net> (raw)
In-Reply-To: <1579443563-12287-1-git-send-email-spujar@nvidia.com>
On Sun, Jan 19, 2020 at 07:49:23PM +0530, Sameer Pujar wrote:
> Crash happens in snd_soc_dapm_new_dai() when substream->private_data
> access is made and substream is NULL here. This is seen for DAIs where
> only playback or capture stream is defined. This seems to be happening
> for codec2codec DAI link.
>
> Both playback and capture are 0 during soc_new_pcm(). This is probably
> happening because cpu_dai and codec_dai are both validated either for
> SNDRV_PCM_STREAM_PLAYBACK or SNDRV_PCM_STREAM_CAPTURE.
>
> Shouldn't be playback = 1 when,
> - playback stream is available for codec_dai AND
> - capture stream is available for cpu_dai
>
> and vice-versa for capture = 1?
>
> Signed-off-by: Sameer Pujar <spujar@nvidia.com>
> ---
> sound/soc/soc-pcm.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/sound/soc/soc-pcm.c b/sound/soc/soc-pcm.c
> index 74d340d..5aa9c0b 100644
> --- a/sound/soc/soc-pcm.c
> +++ b/sound/soc/soc-pcm.c
> @@ -2855,10 +2855,10 @@ int soc_new_pcm(struct snd_soc_pcm_runtime *rtd, int num)
>
> for_each_rtd_codec_dai(rtd, i, codec_dai) {
> if (snd_soc_dai_stream_valid(codec_dai, SNDRV_PCM_STREAM_PLAYBACK) &&
> - snd_soc_dai_stream_valid(cpu_dai, SNDRV_PCM_STREAM_PLAYBACK))
> + snd_soc_dai_stream_valid(cpu_dai, SNDRV_PCM_STREAM_CAPTURE))
> playback = 1;
> if (snd_soc_dai_stream_valid(codec_dai, SNDRV_PCM_STREAM_CAPTURE) &&
> - snd_soc_dai_stream_valid(cpu_dai, SNDRV_PCM_STREAM_CAPTURE))
> + snd_soc_dai_stream_valid(cpu_dai, SNDRV_PCM_STREAM_PLAYBACK))
> capture = 1;
> }
>
There are no longer any playback/capture PCMs registered on
qcom/apq8016_sbc with this patch. :(
With this patch:
$ ls /dev/snd
controlC0 timer
Without this patch:
$ ls /dev/snd
controlC0 pcmC0D0p pcmC0D1c timer
(There is exactly one playback-only and capture-only PCM normally...)
The routing looks like this:
qcom-apq8016-sbc 7702000.sound: ASoC: registered pcm #0 WCD multicodec-0
qcom-apq8016-sbc 7702000.sound: multicodec <-> Primary MI2S mapping ok
qcom-apq8016-sbc 7702000.sound: ASoC: registered pcm #1 WCD-Capture multicodec-1
qcom-apq8016-sbc 7702000.sound: multicodec <-> Tertiary MI2S mapping ok
WCD: connected DAI link 7708000.lpass:Primary Playback -> 771c000.codec:AIF1 Playback
WCD: connected DAI link 7708000.lpass:Primary Playback -> 200f000.spmi:pm8916@1:codec@f00:PDM Playback
WCD-Capture: connected DAI link 771c000.codec:AIF1 Capture -> 7708000.lpass:Tertiary Capture
WCD-Capture: connected DAI link 200f000.spmi:pm8916@1:codec@f00:PDM Capture -> 7708000.lpass:Tertiary Capture
For the playback stream, codec_dai and cpu_dai (lpass) only support SNDRV_PCM_STREAM_PLAYBACK.
The same applies to the capture stream.
I'm a bit confused about this patch, isn't SNDRV_PCM_STREAM_PLAYBACK
used for both cpu_dai and codec_dai in the playback case?
Thanks,
Stephan
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
WARNING: multiple messages have this Message-ID (diff)
From: Stephan Gerhold <stephan@gerhold.net>
To: Sameer Pujar <spujar@nvidia.com>
Cc: tiwai@suse.com, perex@perex.cz, alsa-devel@alsa-project.org,
broonie@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [alsa-devel] [RFC] ASoC: soc-pcm: crash in snd_soc_dapm_new_dai
Date: Mon, 17 Feb 2020 15:41:20 +0100 [thread overview]
Message-ID: <20200217144120.GA243254@gerhold.net> (raw)
In-Reply-To: <1579443563-12287-1-git-send-email-spujar@nvidia.com>
On Sun, Jan 19, 2020 at 07:49:23PM +0530, Sameer Pujar wrote:
> Crash happens in snd_soc_dapm_new_dai() when substream->private_data
> access is made and substream is NULL here. This is seen for DAIs where
> only playback or capture stream is defined. This seems to be happening
> for codec2codec DAI link.
>
> Both playback and capture are 0 during soc_new_pcm(). This is probably
> happening because cpu_dai and codec_dai are both validated either for
> SNDRV_PCM_STREAM_PLAYBACK or SNDRV_PCM_STREAM_CAPTURE.
>
> Shouldn't be playback = 1 when,
> - playback stream is available for codec_dai AND
> - capture stream is available for cpu_dai
>
> and vice-versa for capture = 1?
>
> Signed-off-by: Sameer Pujar <spujar@nvidia.com>
> ---
> sound/soc/soc-pcm.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/sound/soc/soc-pcm.c b/sound/soc/soc-pcm.c
> index 74d340d..5aa9c0b 100644
> --- a/sound/soc/soc-pcm.c
> +++ b/sound/soc/soc-pcm.c
> @@ -2855,10 +2855,10 @@ int soc_new_pcm(struct snd_soc_pcm_runtime *rtd, int num)
>
> for_each_rtd_codec_dai(rtd, i, codec_dai) {
> if (snd_soc_dai_stream_valid(codec_dai, SNDRV_PCM_STREAM_PLAYBACK) &&
> - snd_soc_dai_stream_valid(cpu_dai, SNDRV_PCM_STREAM_PLAYBACK))
> + snd_soc_dai_stream_valid(cpu_dai, SNDRV_PCM_STREAM_CAPTURE))
> playback = 1;
> if (snd_soc_dai_stream_valid(codec_dai, SNDRV_PCM_STREAM_CAPTURE) &&
> - snd_soc_dai_stream_valid(cpu_dai, SNDRV_PCM_STREAM_CAPTURE))
> + snd_soc_dai_stream_valid(cpu_dai, SNDRV_PCM_STREAM_PLAYBACK))
> capture = 1;
> }
>
There are no longer any playback/capture PCMs registered on
qcom/apq8016_sbc with this patch. :(
With this patch:
$ ls /dev/snd
controlC0 timer
Without this patch:
$ ls /dev/snd
controlC0 pcmC0D0p pcmC0D1c timer
(There is exactly one playback-only and capture-only PCM normally...)
The routing looks like this:
qcom-apq8016-sbc 7702000.sound: ASoC: registered pcm #0 WCD multicodec-0
qcom-apq8016-sbc 7702000.sound: multicodec <-> Primary MI2S mapping ok
qcom-apq8016-sbc 7702000.sound: ASoC: registered pcm #1 WCD-Capture multicodec-1
qcom-apq8016-sbc 7702000.sound: multicodec <-> Tertiary MI2S mapping ok
WCD: connected DAI link 7708000.lpass:Primary Playback -> 771c000.codec:AIF1 Playback
WCD: connected DAI link 7708000.lpass:Primary Playback -> 200f000.spmi:pm8916@1:codec@f00:PDM Playback
WCD-Capture: connected DAI link 771c000.codec:AIF1 Capture -> 7708000.lpass:Tertiary Capture
WCD-Capture: connected DAI link 200f000.spmi:pm8916@1:codec@f00:PDM Capture -> 7708000.lpass:Tertiary Capture
For the playback stream, codec_dai and cpu_dai (lpass) only support SNDRV_PCM_STREAM_PLAYBACK.
The same applies to the capture stream.
I'm a bit confused about this patch, isn't SNDRV_PCM_STREAM_PLAYBACK
used for both cpu_dai and codec_dai in the playback case?
Thanks,
Stephan
next prev parent reply other threads:[~2020-02-17 14:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-19 14:19 [alsa-devel] [RFC] ASoC: soc-pcm: crash in snd_soc_dapm_new_dai Sameer Pujar
2020-01-19 14:19 ` Sameer Pujar
2020-01-21 17:28 ` [alsa-devel] Applied "ASoC: soc-pcm: crash in snd_soc_dapm_new_dai" to the asoc tree Mark Brown
2020-01-21 17:28 ` Mark Brown
2020-01-23 9:55 ` [alsa-devel] [RFC] ASoC: soc-pcm: crash in snd_soc_dapm_new_dai Sameer Pujar
2020-01-23 9:55 ` Sameer Pujar
2020-02-17 14:41 ` Stephan Gerhold [this message]
2020-02-17 14:41 ` [alsa-devel] " Stephan Gerhold
2020-02-17 15:43 ` Mark Brown
2020-02-17 15:43 ` Mark Brown
2020-02-17 17:12 ` Stephan Gerhold
2020-02-17 17:12 ` Stephan Gerhold
2020-02-17 17:19 ` Stephan Gerhold
2020-02-17 17:19 ` Stephan Gerhold
2020-02-17 17:30 ` Mark Brown
2020-02-17 17:30 ` Mark Brown
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=20200217144120.GA243254@gerhold.net \
--to=stephan@gerhold.net \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=spujar@nvidia.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.