From: Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: audio-graph-card2: use correct endpoint when getting link parameters
Date: Tue, 21 Jan 2025 08:23:49 +0200 [thread overview]
Message-ID: <cb602ae2-dd56-4f38-95be-c855afe6b9e4@gmail.com> (raw)
In-Reply-To: <87h65t3voj.wl-kuninori.morimoto.gx@renesas.com>
Hi Morimoto-san,
On 21.01.25 г. 1:35 ч., Kuninori Morimoto wrote:
>
> Hi Ivaylo
>
> Thank you for the patch
>
>> When link DT nodes are parsed, most functions get port as a parameter,
>> which results in port endpoint@0 always being used. However, each endpoint
>> might have different settings, but those are currently ignored.
>>
>> Fix that by passing endpoint instead of port when parsing link parameters.
>>
>> Signed-off-by: Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>
>> ---
> (snip)
>> @@ -831,9 +830,8 @@ int audio_graph2_link_normal(struct simple_util_priv *priv,
>> struct device_node *lnk,
>> struct link_info *li)
>> {
>> - struct device_node *cpu_port = lnk;
>> - struct device_node *cpu_ep __free(device_node) = of_graph_get_next_port_endpoint(cpu_port, NULL);
>> - struct device_node *codec_port __free(device_node) = of_graph_get_remote_port(cpu_ep);
>> + struct device_node *cpu_ep __free(device_node) = of_graph_get_next_port_endpoint(lnk, NULL);
>> + struct device_node *codec_ep __free(device_node) = of_graph_get_remote_endpoint(cpu_ep);
>> int ret;
>
> You don't need to change cpu_port/cpu_ep here ?
> And, I would like to keep "cpu_port = lnk" here.
>
cpu_port will be used on the next line only, but ok, will send v2 with
the above changes.
Thanks,
Ivo
> Except above
> Acked-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
>
> Thank you for your help !!
>
> Best regards
> ---
> Kuninori Morimoto
next prev parent reply other threads:[~2025-01-21 6:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 7:11 [RFC PATCH] soc: audio-graph-card2: use correct endpoint when getting link parameters Ivaylo Dimitrov
2025-01-13 5:55 ` Ivaylo Dimitrov
2025-01-13 13:40 ` Mark Brown
2025-01-13 16:24 ` Ivaylo Dimitrov
2025-01-13 17:01 ` Mark Brown
2025-01-13 21:38 ` Ivaylo Dimitrov
2025-01-14 6:44 ` Kuninori Morimoto
2025-01-14 9:04 ` Ivaylo Dimitrov
2025-01-14 23:49 ` Kuninori Morimoto
2025-01-15 6:10 ` Ivaylo Dimitrov
2025-01-20 16:27 ` [PATCH] ASoC: " Ivaylo Dimitrov
2025-01-20 23:35 ` Kuninori Morimoto
2025-01-21 6:23 ` Ivaylo Dimitrov [this message]
2025-01-21 6:48 ` [PATCH v2] " Ivaylo Dimitrov
2025-01-21 12:18 ` Mark Brown
2025-01-21 13:33 ` Ivaylo Dimitrov
2025-01-21 13:41 ` Mark Brown
2025-01-21 23:22 ` Kuninori Morimoto
2025-01-23 11:29 ` Mark Brown
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=cb602ae2-dd56-4f38-95be-c855afe6b9e4@gmail.com \
--to=ivo.g.dimitrov.75@gmail.com \
--cc=broonie@kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@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