From: Jiada Wang <jiada_wang@mentor.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Mark Brown <broonie@kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Linux-Kernel <linux-kernel@vger.kernel.org>,
Linux-ALSA <alsa-devel@alsa-project.org>,
Liam Girdwood <lgirdwood@gmail.com>, <dragos_tarcatu@mentor.com>,
<twischer@de.adit-jv.com>, <tiwai@suse.com>, <perex@perex.cz>
Subject: Re: [PATCH linux-next 01/10] ASoC: rsnd: ssi: Request dedicated dma channels for busif1 to 7
Date: Tue, 2 Oct 2018 16:52:24 +0900 [thread overview]
Message-ID: <01535cc6-bd85-aec1-b0ce-7ea9e60533d0@mentor.com> (raw)
In-Reply-To: <87k1n6trsf.wl-kuninori.morimoto.gx@renesas.com>
Hi Morimoto-san
On 2018/09/28 9:08, Kuninori Morimoto wrote:
> Hi Jiada
> Cc: linux-renesas-soc ML
>
> Thank you for your patch
>
>> From: Jiada Wang <jiada_wang@mentor.com>
>>
>> Currently ssi driver only request dma channel for SSI_0,
>> which is used to transfer data to/from busif0.
>>
>> But since busif1 to busif7 also maybe used, dedicated dma channels
>> are request for data transfer between these busif.
>>
>> Signed-off-by: Jiada Wang <jiada_wang@mentor.com>
>> ---
> (snip)
>> @@ -938,12 +940,20 @@ static struct dma_chan *rsnd_ssi_dma_req(struct rsnd_dai_stream *io,
>> {
>> struct rsnd_priv *priv = rsnd_mod_to_priv(mod);
>> int is_play = rsnd_io_is_play(io);
>> - char *name;
>> + int busif = rsnd_ssi_get_busif(io);
>> + char name[SSI_DMA_NAME_SIZE];
>>
>> - if (rsnd_ssi_use_busif(io))
>> - name = is_play ? "rxu" : "txu";
>> - else
>> - name = is_play ? "rx" : "tx";
>> + if (rsnd_ssi_use_busif(io)) {
>> + if (is_play)
>> + snprintf(name, SSI_DMA_NAME_SIZE, "rxu%d", busif);
>> + else
>> + snprintf(name, SSI_DMA_NAME_SIZE, "txu%d", busif);
>> + } else {
>> + if (is_play)
>> + snprintf(name, SSI_DMA_NAME_SIZE, "rx");
>> + else
>> + snprintf(name, SSI_DMA_NAME_SIZE, "tx");
>> + }
> Unfortunately, this patch breaks "git bisect", and Gen2 platforms.
> We need to keep existing "rxu/txu" more. Please consider compatibility.
> # we can remove it 2 or 3 version later ?
>
> If the commit which has this patch, but doesn't have [02/xx] or later,
> it can't use BUSIF.
>
> And your patch doesn't care Gen2 series.
> DT compatibility is very sensitive...
Thanks for your review comments, I will send out v2 patch set to take
care of GEN2 series,
and move this patch after other DT related patches
Thanks,
Jiada
next prev parent reply other threads:[~2018-10-02 7:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 5:03 [PATCH linux-next 00/10] ASoC: rsnd: support to set different busif jiada_wang
2018-09-27 5:03 ` [PATCH linux-next 01/10] ASoC: rsnd: ssi: Request dedicated dma channels for busif1 to 7 jiada_wang
2018-09-28 0:08 ` Kuninori Morimoto
2018-10-02 7:52 ` Jiada Wang [this message]
2018-09-27 5:03 ` [PATCH linux-next 02/10] arm64: r8a7795: add dma request number for busif1 ~ busif7 jiada_wang
2018-09-27 5:04 ` [PATCH linux-next 03/10] arm64: r8a7796: " jiada_wang
2018-09-27 5:04 ` [PATCH linux-next 04/10] arm64: r8a774a1: " jiada_wang
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=01535cc6-bd85-aec1-b0ce-7ea9e60533d0@mentor.com \
--to=jiada_wang@mentor.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=dragos_tarcatu@mentor.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=twischer@de.adit-jv.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).