From: Sameer Pujar <spujar@nvidia.com>
To: alsa-devel@alsa-project.org,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
devicetree@vger.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, spujar@nvidia.com
Subject: Query on audio-graph-card DT binding
Date: Tue, 26 Dec 2023 21:58:02 +0530 [thread overview]
Message-ID: <dfe363ef-4638-4b5e-8308-73e286ac0b50@nvidia.com> (raw)
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?
Thanks,
Sameer.
next reply other threads:[~2023-12-26 16:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-26 16:28 Sameer Pujar [this message]
2024-01-03 7:02 ` ASoC: dt-bindings: Query on audio-graph-card DT binding Sameer Pujar
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=dfe363ef-4638-4b5e-8308-73e286ac0b50@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