devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Sameer Pujar <spujar@nvidia.com>
Cc: alsa-devel@alsa-project.org,
	Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
	devicetree@vger.kernel.org, Mark Brown <broonie@kernel.org>,
	robh+dt@kernel.org, Jon Hunter <jonathanh@nvidia.com>,
	linux-tegra@vger.kernel.org
Subject: Re: Query on audio-graph-card DT binding
Date: Thu, 4 Jan 2024 18:07:22 +0100	[thread overview]
Message-ID: <ZZblyhfzQjzyoUc_@orome.fritz.box> (raw)
In-Reply-To: <dfe363ef-4638-4b5e-8308-73e286ac0b50@nvidia.com>

[-- Attachment #1: Type: text/plain, Size: 1527 bytes --]

On Tue, Dec 26, 2023 at 09:58:02PM +0530, Sameer Pujar wrote:
> Hi Morimoto-san,
> 
> This question is regarding audio-graph-card.c driver related DT binding.
> 
> I am looking to enable following DAI link connection in device tree for
> Tegra audio:
> 
>               /-----> codec1 endpoint
>              /
> CPU endpoint \
>               \-----> codec2 endpoint
> 
> 
> I see that, "remote-endpoint" property can only specify single phandle
> object for connection to a remote endpoint. In other words, the link can be
> one-to-one. For illustration, please see below example. However I see it
> leads to a build error if phandle-array is provided for "remote-endpoint"
> property.
> 
>  cpu_port {
>      cpu_ep: endpoint {
>          remote-endpoint = <&codec1_ep>, <&codec2_ep>;
>      };
>  };
> 
>  codec1 {
>      codec1_ep: endpoint {
>          remote-endpoint = <&cpu_ep>;
>      };
>  };
> 
>  codec2 {
>      codec2_ep: endpoint {
>          remote-endpoint = <&cpu_ep>;
>      };
>  };
> 
> Is there a possibility to re-use the same CPU endpoint for connecting to
> multiple codec endpoints like shown in above example?

Can you describe the use-case? Is there a need to switch between codec1
and codec2 endpoints or do they receive the same data in parallel all
the time?

Could this perhaps be described by adding multiple CPU ports with one
endpoint each?

Thierry

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2024-01-04 17:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-26 16:28 Query on audio-graph-card DT binding Sameer Pujar
2024-01-03  7:02 ` ASoC: dt-bindings: " Sameer Pujar
2024-01-04 17:07 ` Thierry Reding [this message]
2024-01-04 17:22   ` Mark Brown
2024-01-05  4:54     ` Sameer Pujar
2024-01-05  8:11       ` Thierry Reding
2024-01-05 11:19         ` Sameer Pujar
2024-01-09  2:17           ` Kuninori Morimoto
2024-01-09 11:49             ` Sameer Pujar
2024-01-09 23:15               ` Kuninori Morimoto
2024-01-10  5:01                 ` Sameer Pujar
2024-01-11  0:44                   ` Kuninori Morimoto
2024-01-11  4:28                     ` Sameer Pujar
2024-01-11  4:56                       ` Kuninori Morimoto
2024-01-11  5:09                         ` Sameer Pujar
2024-01-11  5:32                           ` Kuninori Morimoto
2024-01-11  6:49                             ` Sameer Pujar
2024-01-11 22:59                               ` Kuninori Morimoto
2024-01-12  8:09                                 ` Sameer Pujar
2024-01-15  1:43                                   ` 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=ZZblyhfzQjzyoUc_@orome.fritz.box \
    --to=thierry.reding@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=linux-tegra@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=spujar@nvidia.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;
as well as URLs for NNTP newsgroup(s).