From: Jiada Wang <jiada_wang@mentor.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: <lgirdwood@gmail.com>, <broonie@kernel.org>, <perex@perex.cz>,
<tiwai@suse.com>, <alsa-devel@alsa-project.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [alsa-devel] [PATCH linux-next v2 9/9] ASoC: rsnd: add busif property to dai stream
Date: Thu, 4 Oct 2018 11:43:18 +0900 [thread overview]
Message-ID: <557e63d1-dbb7-4232-b53e-4a5499024180@mentor.com> (raw)
In-Reply-To: <87va6ipkaz.wl-kuninori.morimoto.gx@renesas.com>
Hi Morimoto-san
On 2018/10/04 10:41, Kuninori Morimoto wrote:
> Hi Jiada
>
> Thank you for your patch
>
>> in GEN3 SSI may use different BUSIF for data transfer,
>> this patch adds busif property to each dai stream,
>> to indicate the BUSIF used by playback/capture stream.
>>
>> Also adds rsnd_ssi_select_busif() to automatically select
>> BUSIF (currently only BUSIF0 is selected)
>>
>> Signed-off-by: Jiada Wang <jiada_wang@mentor.com>
>> ---
>> sound/soc/sh/rcar/core.c | 3 +++
>> sound/soc/sh/rcar/dma.c | 31 +++++++++++++++++++++++++++++++
>> sound/soc/sh/rcar/rsnd.h | 3 +++
>> sound/soc/sh/rcar/ssi.c | 30 +++++++++++++++++++++++++++++-
>> 4 files changed, 66 insertions(+), 1 deletion(-)
>>
>> diff --git a/sound/soc/sh/rcar/core.c b/sound/soc/sh/rcar/core.c
>> index 40d7dc4f7839..5e3e6e65bcdf 100644
>> --- a/sound/soc/sh/rcar/core.c
>> +++ b/sound/soc/sh/rcar/core.c
>> @@ -1158,6 +1158,9 @@ static int rsnd_hw_params(struct snd_pcm_substream *substream,
>> struct rsnd_dai *rdai = rsnd_dai_to_rdai(dai);
>> struct rsnd_dai_stream *io = rsnd_rdai_to_io(rdai, substream);
>> int ret;
>> + int chan = rsnd_runtime_channel_for_ssi_with_params(io, hw_params);
>> +
>> + rsnd_ssi_select_busif(io, chan);
> If my understanding was correct, the chance to use BUSIFx is when TDM split mode.
Yes, only when SSI works in Split/Ex-Split mode, BUSIFx other than 0 is
necessary
> And this patch selects it on runtime (= hw_param) ?
Because, in order to automatically determine BUSIF number,
information like SSI mode (non-Split/Split/Ex-Split), runtime channel,
are required
(in our internal implementation, SSI mode is selected by kctrl)
because of this, in this patch, BUSIF is selected on runtime
> But, I think we can/should select it on probe timing from DT connection.
> Am I misunderstanding ?
with the above reasoning, BUSIF is selected on runtime.
what do you think?
Thanks,
Jiada
> I'm not sure how to select, but adding new ssiuX0 - ssiuX7
> is realistic idea (parse sound card is not realistic...) ?
> If so, your rxu/txu DMA can be more simple ?
next prev parent reply other threads:[~2018-10-04 2:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-03 9:01 jiada_wang
2018-10-04 1:41 ` [alsa-devel] " Kuninori Morimoto
2018-10-04 2:43 ` Jiada Wang [this message]
2018-10-04 3:43 ` Kuninori Morimoto
2018-10-04 7:00 ` Jiada Wang
2018-10-09 0:44 ` Kuninori Morimoto
2018-10-09 7:09 ` Jiada Wang
2018-10-09 7:47 ` Kuninori Morimoto
2018-10-09 10:40 ` Jiada Wang
2018-10-10 0:16 ` Kuninori Morimoto
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=557e63d1-dbb7-4232-b53e-4a5499024180@mentor.com \
--to=jiada_wang@mentor.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®