From: "Alvin Šipraga" <alvin.sipraga@analog.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Mark Brown <broonie@kernel.org>, linux-sound@vger.kernel.org
Subject: Re: [PATCH 07/10] ASoC: soc-dai: rename snd_soc_dai_stream_active()
Date: Tue, 15 Sep 2026 03:00:20 +0200 [thread overview]
Message-ID: <aqiS7yz4IIYzU6ml@analog.com> (raw)
In-Reply-To: <87h5jsli4y.wl-kuninori.morimoto.gx@renesas.com>
Hi Kuninori,
On Mon, Sep 14, 2026 at 01:46:21AM +0000, Kuninori Morimoto wrote:
> snd_soc_dai_stream_active() (A) and snd_soc_dai_active() (B) are almost
> same function, but implemented different place with different naming.
>
> Let's move snd_soc_dai_stream_active() (A) prev to snd_soc_dai_active()
> (B), and rename it (C).
>
> (C)+ snd_soc_dai_active_stream()
> (B) snd_soc_dai_active()
> ...
> (A)- snd_soc_dai_stream_active()
I found this rename quite confusing.
Normally I read a function like snd_soc_dai_steam_active(x, y) to mean
"is stream y of dai x active"? We also have snd_soc_dai_stream_valid()
which has similar semantics.
OTOH snd_soc_dai_active_stream() sounds like "what's the active stream
of the DAI?" (which of course doesn't make sense; could be that both or
neither are active).
I sense you're trying to "namespace" all the dai->stream[dir].active
logic under functions named snd_soc_dai_active_xxx(), which is
understandable, but don't you think the following is cleaner?
snd_soc_dai_action() <=> similar to snd_soc_runtime_action()
snd_soc_dai_active() <=> is (any) DAI stream active?
snd_soc_dai_stream_active() <=> is (given) DAI stream active?
BTW, maybe patches 7-9 should be one patch? It might make the review a
bit easier.
Kind regards,
Alvin
next prev parent reply other threads:[~2026-09-15 1:00 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 1:43 [PATCH 00/10] ASoC: add new DAI functions Kuninori Morimoto
2026-09-14 1:43 ` [PATCH 01/10] ASoC: soc-dai: add snd_soc_dai_id() Kuninori Morimoto
2026-09-15 13:43 ` Alvin Šipraga
2026-09-15 13:43 ` Alvin Šipraga
2026-09-15 13:43 ` Alvin Šipraga
2026-09-14 1:43 ` [PATCH 02/10] ASoC: soc-dai: add snd_soc_dai_to_component() Kuninori Morimoto
2026-09-15 13:44 ` Alvin Šipraga
2026-09-14 1:43 ` [PATCH 03/10] ASoC: soc-dai: add snd_soc_dai_to_driver() Kuninori Morimoto
2026-09-15 13:44 ` Alvin Šipraga
2026-09-14 1:43 ` [PATCH 04/10] ASoC: soc-dai: add snd_soc_dai_{to/from}_list() Kuninori Morimoto
2026-09-15 15:03 ` Alvin Šipraga
2026-09-15 23:37 ` Kuninori Morimoto
2026-09-14 1:45 ` [PATCH 05/10] ASoC: soc-dai: add snd_soc_dai_symmetric_get_params() Kuninori Morimoto
2026-09-15 1:51 ` Alvin Šipraga
2026-09-15 4:30 ` Kuninori Morimoto
2026-09-14 1:46 ` [PATCH 06/10] ASoC: soc-dai: add snd_soc_dai_{set/to}_priv() Kuninori Morimoto
2026-09-14 8:38 ` Charles Keepax
2026-09-15 15:05 ` Alvin Šipraga
2026-09-14 1:46 ` [PATCH 07/10] ASoC: soc-dai: rename snd_soc_dai_stream_active() Kuninori Morimoto
2026-09-15 1:00 ` Alvin Šipraga [this message]
2026-09-15 5:20 ` Kuninori Morimoto
2026-09-15 13:42 ` Alvin Šipraga
2026-09-16 0:48 ` Kuninori Morimoto
2026-09-16 1:13 ` Alvin Šipraga
2026-09-16 1:45 ` Kuninori Morimoto
2026-09-14 1:46 ` [PATCH 08/10] ASoC: soc-dai: rename snd_soc_dai_action() Kuninori Morimoto
2026-09-14 1:46 ` [PATCH 09/10] ASoC: soc-dai: move snd_soc_dai_active_action() to soc-internal.h Kuninori Morimoto
2026-09-14 1:47 ` [PATCH 10/10] ASoC: soc-dai: add snd_soc_dai_get_bclk() Kuninori Morimoto
2026-09-14 13:55 ` Mark Brown
2026-09-14 23:56 ` Kuninori Morimoto
2026-09-15 15:19 ` Alvin Šipraga
2026-09-15 23:38 ` Kuninori Morimoto
2026-09-14 13:37 ` [PATCH 00/10] ASoC: add new DAI functions Mark Brown
2026-09-15 0:05 ` 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=aqiS7yz4IIYzU6ml@analog.com \
--to=alvin.sipraga@analog.com \
--cc=broonie@kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-sound@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.