From: Arnaud Pouliquen <arnaud.pouliquen@st.com>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>,
	Vinod Koul <vinod.koul@intel.com>
Cc: Takashi Iwai <tiwai@suse.de>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"broonie@kernel.org" <broonie@kernel.org>,
	Charles Keepax <ckeepax@opensource.wolfsonmicro.com>,
	"lgirdwood@gmail.com" <lgirdwood@gmail.com>
Subject: Re: [RFC v2 1/3] ASoC: core: allow DAI PCM controls bound to PCM device
Date: Thu, 24 Nov 2016 10:52:59 +0100	[thread overview]
Message-ID: <c20f7a0f-0860-3d3b-f518-6a33661cd11e@st.com> (raw)
In-Reply-To: <1f53b56a-719c-4711-59eb-ba11a42f3773@sakamocchi.jp>
Hello Vinod
On 11/24/2016 06:14 AM, Takashi Sakamoto wrote:
>> The same problem (same control names IIUC) existis on codec and SoC's, now
>> that both have DSP, we can have DSP "Volume control"...
>>
>> Would this solve that as well..?
> 
> No. It's not the aim of this patchset and out of its scope.
> 
> However, in fact, we should seek good solution for the issue of
> 'conflict of identification information of control element set added by
> ALSA SoC part automatically'.
>
Solution only solves issue for DAIs that are statically linked to a PCM
device on probe,
In you case, link to PCM device is done during runtime through adpcm, right?
Have you an example of a PCM control that you need to link to the PCM
character device?
>>> Application should be able to address the control using the
>>> device field number, according to the PCM character device.
>>> This patch allows to link DAI PCM controls to the PCM device.
>>
>> why is that part required..? Is the problem being solved to address a
>> control uniquely or something else?
It treats a PCM control uniquely,
 what do you have in mind when you say "or something else"?
>>
>>> During DAI_link probe, PCM controls are added after device field is forced
>>> to the PCM device number.
>>>
>>> Signed-off-by: Arnaud Pouliquen <arnaud.pouliquen@st.com>
>>> ---
>>>  include/sound/soc-dai.h |  4 ++++
>>>  sound/soc/soc-core.c    | 37 +++++++++++++++++++++++++++++++++++++
>>>  2 files changed, 41 insertions(+)
Regards,
Arnaud
next prev parent reply	other threads:[~2016-11-24  9:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-22 10:53 [RFC v2 0/3] ALSA controls management using index/device/sub-devices fields Arnaud Pouliquen
2016-11-22 10:53 ` [RFC v2 1/3] ASoC: core: allow DAI PCM controls bound to PCM device Arnaud Pouliquen
2016-11-24  4:55   ` Vinod Koul
2016-11-24  5:14     ` Takashi Sakamoto
2016-11-24  9:52       ` Arnaud Pouliquen [this message]
2016-11-22 10:53 ` [RFC v2 2/3] ASoC: sti: bind pcm controls to pcm device Arnaud Pouliquen
2016-11-22 10:53 ` [RFC v2 3/3] ASoC: hdmi-codec: Example of PCM control bound to PCM device for multi HDMI DAIs Arnaud Pouliquen
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=c20f7a0f-0860-3d3b-f518-6a33661cd11e@st.com \
    --to=arnaud.pouliquen@st.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=ckeepax@opensource.wolfsonmicro.com \
    --cc=lgirdwood@gmail.com \
    --cc=o-takashi@sakamocchi.jp \
    --cc=tiwai@suse.de \
    --cc=vinod.koul@intel.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;
as well as URLs for NNTP newsgroup(s).