From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
To: Arnaud Pouliquen <arnaud.pouliquen@st.com>
Cc: Brian Norris <briannorris@chromium.org>,
Linux-ALSA <alsa-devel@alsa-project.org>,
Mark Brown <broonie@kernel.org>, Johan Hovold <johan@kernel.org>
Subject: Re: [Test Request v2] Component level pcm_new/pcm_free v2
Date: Mon, 24 Jul 2017 23:10:41 +0000 [thread overview]
Message-ID: <87eft577yl.wl%kuninori.morimoto.gx@renesas.com> (raw)
In-Reply-To: <3d74148b-0535-2353-6284-1ad5b5ee3a72@st.com>
Hi Arnaud
> > These are v2 of Component level pcm_new/free patches v2.
> > Previous patch-set still had issue if 2 platform were registered.
> > I think this version solved this issue.
> > But, I'm not sure if you are using unexpected usage which I don't use.
> > So, can you please test these patches ?
> > replacing platform to component is based on this patch-set
>
> I came across the issue last week on V4.12 (without your V1 patches).
> I reproduced issue with my driver:
> https://patchwork.kernel.org/patch/9630821/
> I declared 2 DAIs with associated platform. pcm_new ops was call twice
> times.
>
> Applying your patches solves my issue.
>
> Tested-by: Arnaud Pouliquen <arnaud.pouliquen@st.com>
Thank you for your testing
I'm happy to hear about that.
Best regards
---
Kuninori Morimoto
prev parent reply other threads:[~2017-07-24 23:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-21 4:05 [Test Request v2] Component level pcm_new/pcm_free v2 Kuninori Morimoto
2017-07-21 4:08 ` [Test Request v2 1/3] ASoC: soc-core: add snd_soc_rtdcom_xxx() Kuninori Morimoto
2017-07-21 4:09 ` [Test Request v2 2/3] ASoC: use snd_soc_rtdcom_add() and convert to consistent operation Kuninori Morimoto
2017-08-10 15:41 ` Applied "ASoC: use snd_soc_rtdcom_add() and convert to consistent operation" to the asoc tree Mark Brown
2017-07-21 4:09 ` [Test Request v2 3/3] ASoC: add Component level pcm_new/pcm_free v2 Kuninori Morimoto
2017-07-24 16:31 ` [Test Request v2] " Arnaud Pouliquen
2017-07-24 23:10 ` Kuninori Morimoto [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=87eft577yl.wl%kuninori.morimoto.gx@renesas.com \
--to=kuninori.morimoto.gx@renesas.com \
--cc=alsa-devel@alsa-project.org \
--cc=arnaud.pouliquen@st.com \
--cc=briannorris@chromium.org \
--cc=broonie@kernel.org \
--cc=johan@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).