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>, <twischer@de.adit-jv.com>,
<dragos_tarcatu@mentor.com>, <alsa-devel@alsa-project.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH linux-next 09/10] ASoC: rsnd: add busif property to dai stream
Date: Tue, 2 Oct 2018 16:58:24 +0900 [thread overview]
Message-ID: <042e51bb-7c48-9145-51f2-b6687c044c19@mentor.com> (raw)
In-Reply-To: <87in2qtr6f.wl-kuninori.morimoto.gx@renesas.com>
Hi Morimoto-san
On 2018/09/28 9:21, Kuninori Morimoto wrote:
> Hi Jiada
>
>
>> 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.
> (snip)
>> + io_playback->busif = rsnd_busif_get(priv, dai_i);
>> + io_capture->busif = rsnd_busif_get(priv, rsnd_rdai_nr(priv) + dai_i);
> (snip)
>> + busif = devm_kcalloc(dev, 2 * nr, sizeof(*busif), GFP_KERNEL);
> (snip)
>> @@ -456,6 +456,7 @@ struct rsnd_dai_stream {
>> struct rsnd_mod *dma;
>> struct rsnd_dai *rdai;
>> struct device *dmac_dev; /* for IPMMU */
>> + struct rsnd_kctrl_cfg_s *busif;
>> u32 parent_ssi_status;
>> };
> It looks very complex to me.
> Why don't you just have "busif" on rsnd_dai_stream, instead of "*busif" ?
yes, it can be replaced with *busif instead,
but it will result in some reorder of declarations in rsnd.h
will update this patch in v2 patch set.
Thanks,
Jiada
>> int rsnd_ssi_get_busif(struct rsnd_dai_stream *io)
>> {
>> - return 0; /* BUSIF0 only for now */
>> + if (!rsnd_ssi_use_busif(io))
>> + return 0;
>> +
>> + return io->busif->val;
>> }
> Who/How update val ?
>
prev parent reply other threads:[~2018-10-02 7:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 5:12 jiada_wang
2018-09-28 0:21 ` Kuninori Morimoto
2018-10-02 7:58 ` Jiada Wang [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=042e51bb-7c48-9145-51f2-b6687c044c19@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=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
all inboxes | Powered by JetHome®