linux-tegra.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sameer Pujar <spujar@nvidia.com>
To: alsa-devel@alsa-project.org,
	Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
	devicetree@vger.kernel.org, robh+dt@kernel.org,
	Mark Brown <broonie@kernel.org>
Cc: Mark Brown <broonie@kernel.org>,
	robh+dt@kernel.org, Thierry Reding <thierry.reding@gmail.com>,
	Jon Hunter <jonathanh@nvidia.com>,
	linux-tegra@vger.kernel.org
Subject: ASoC: dt-bindings: Query on audio-graph-card DT binding
Date: Wed, 3 Jan 2024 12:32:07 +0530	[thread overview]
Message-ID: <b041d536-213f-490e-a83f-d86fc4149eaa@nvidia.com> (raw)
In-Reply-To: <dfe363ef-4638-4b5e-8308-73e286ac0b50@nvidia.com>

Hi Rob, Mark, Morimoto-san


Build error in the example mentioned earlier seems to be expected since 
it requires one to one connection between remote endpoints.

Pasting the error I get:

DTC arch/arm64/boot/dts/nvidia/tegra234-p3737-0000+p3701-0000.dtb
dtc: scripts/dtc/livetree.c:437: propval_cell: Assertion `prop->val.len 
== sizeof(cell_t)' failed.
Aborted (core dumped)
make[3]: *** [scripts/Makefile.lib:419: 
arch/arm64/boot/dts/nvidia/tegra234-p3737-0000+p3701-0000.dtb] Error 134
make[2]: *** [scripts/Makefile.build:480: arch/arm64/boot/dts/nvidia] 
Error 2
make[1]: *** [/home/spujar/upstream/kernel/Makefile:1476: dtbs] Error 2
make[1]: *** Waiting for unfinished jobs....
   CALL    scripts/checksyscalls.sh
make: *** [Makefile:234: __sub-make] Error 2
Execution failed.

Given this, how an endpoint can be shared? Is only solution is to create 
dummy endpoints for CPU and connect them to each codec?
Can you please suggest how this can be addressed?

> 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?
>


  reply	other threads:[~2024-01-03  7:02 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 ` Sameer Pujar [this message]
2024-01-04 17:07 ` Thierry Reding
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=b041d536-213f-490e-a83f-d86fc4149eaa@nvidia.com \
    --to=spujar@nvidia.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=thierry.reding@gmail.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).