public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: lgirdwood@gmail.com, broonie@kernel.org, perex@perex.cz,
	tiwai@suse.com, tony@atomide.com, alsa-devel@alsa-project.org,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] soc: audio-graph-card2: use correct endpoint when getting link parameters
Date: Wed, 15 Jan 2025 08:10:03 +0200	[thread overview]
Message-ID: <e2a019da-b8db-4976-8cbe-bbbfac771d38@gmail.com> (raw)
In-Reply-To: <875xmhj6s0.wl-kuninori.morimoto.gx@renesas.com>

Hi Morimoto-san,

On 15.01.25 г. 1:49 ч., Kuninori Morimoto wrote:
> 
> Hi Ivaylo
> 
> Thank you for clarify your situation.
> 
>>> You want to parse "remote" endpoint (= rep) directly, but the function
>>> requests "port" (= rport), and it will use endpoint0 ( != rep).
>>> Is this the main issue you want to fix ?
>>>
>>
>> Yes, it is the 'remote' side endpoint, currently it is always remote
>> endpoint0 that is used, because when you get 'port', it is endpoint0 of
>> that port that core uses.
> 
> OK, I could understand, and I can agree to your idea.
> Getting "port" from "endpoint" is always stable, but getting "endpoint"
> from "port" without parameter will be issue, indeed.
> 
> But I guess your original patch is based on very old kernel ?
> It can't be applied to Mark's for-6.14 branch as-is.
> Please based on latest branch.
> 

Yes, it is based in 6.6, that's why I sent RFC patch, as rebasing will 
not be trivial and I didn't want to spend time on something that could 
possibly be rejected.

> And about git-comment,
> 
> 	When link parameters are parsed, it is always endpoint@0 that is used and
> 	parameters set to other endpoints are ignored.
> 
> Please indicate that current function requests "port" as parameter,
> thus, it always selects endpoint0, etc. That is easy to understand.
> 

Ok, will do.

Thanks!
Ivo

  reply	other threads:[~2025-01-15  6:10 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 [this message]
2025-01-20 16:27       ` [PATCH] ASoC: " Ivaylo Dimitrov
2025-01-20 23:35         ` Kuninori Morimoto
2025-01-21  6:23           ` Ivaylo Dimitrov
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=e2a019da-b8db-4976-8cbe-bbbfac771d38@gmail.com \
    --to=ivo.g.dimitrov.75@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --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=tony@atomide.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