From: Richard Fitzgerald <rf@opensource.cirrus.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: <devicetree@vger.kernel.org>, <alsa-devel@alsa-project.org>,
<patches@opensource.cirrus.com>, <linux-kernel@vger.kernel.org>,
<robh+dt@kernel.org>, <broonie@kernel.org>
Subject: Re: [PATCH 2/2] ASoC: audio_graph_card2: Add support for variable slot widths
Date: Thu, 17 Feb 2022 12:51:50 +0000 [thread overview]
Message-ID: <0ba5f63c-44a4-1949-60dd-f5debd706caa@opensource.cirrus.com> (raw)
In-Reply-To: <87a6eq49yq.wl-kuninori.morimoto.gx@renesas.com>
On 17/02/2022 00:23, Kuninori Morimoto wrote:
>
> Hi Richard
>
> Thank you for your patch.
> One comment from me.
>
>> struct asoc_simple_dai {
>> const char *name;
>> unsigned int sysclk;
>> @@ -26,6 +31,9 @@ struct asoc_simple_dai {
>> unsigned int rx_slot_mask;
>> struct clk *clk;
>> bool clk_fixed;
>> + struct asoc_simple_tdm_width_map *tdm_width_map;
>> + int n_tdm_widths;
>> + struct snd_soc_dai *dai;
>> };
> (snip)
(snip)
> (snip)
>> @@ -386,6 +479,8 @@ static int asoc_simple_init_dai(struct snd_soc_dai *dai,
>> if (!simple_dai)
>> return 0;
>>
>> + simple_dai->dai = dai;
>
> Indeed the relationship between asoc_simple_dai and snd_soc_dai are
> very mystery, and current utils is using confusable naming.
> We want to have some better solution about there.
>
> Having snd_soc_dai pointer inside asoc_simple_dai itself is not bad idea.
> But we can get snd_soc_dai pointer without it.
>
> Please check asoc_simple_dai_init().
> Not tested, but we can replace the code like this ?
>
> => struct snd_soc_dai *dai;
>
> for_each_prop_dai_codec(props, i, pdai) {
> => dai = asoc_rtd_to_codec(rtd, i);
> ret = asoc_simple_set_tdm(dai, pdai, params);
> if (ret < 0)
> return ret;
> }
>
>
I first thought about doing it like that. But I was not sure whether it
is safe to assume [i] is the same entry for both arrays. If it is ok,
then I can use that and do not need to add the snd_soc_dai * to struct
asoc_simple_dai.
I will look at this and send a V2 set if it is ok.
prev parent reply other threads:[~2022-02-17 12:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 17:14 [PATCH 0/2] ASoC: audio_graph_card2: Support variable slot widths Richard Fitzgerald
2022-02-16 17:14 ` [PATCH 1/2] ASoC: dt-bindings: audio-graph-port: Add dai-tdm-slot-width-map Richard Fitzgerald
2022-02-16 17:14 ` [PATCH 2/2] ASoC: audio_graph_card2: Add support for variable slot widths Richard Fitzgerald
2022-02-17 0:23 ` Kuninori Morimoto
2022-02-17 12:51 ` Richard Fitzgerald [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=0ba5f63c-44a4-1949-60dd-f5debd706caa@opensource.cirrus.com \
--to=rf@opensource.cirrus.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=robh+dt@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 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).