From: Sameer Pujar <spujar@nvidia.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Thierry Reding <thierry.reding@gmail.com>,
Mark Brown <broonie@kernel.org>,
alsa-devel@alsa-project.org, devicetree@vger.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, 11 Jan 2024 10:39:50 +0530 [thread overview]
Message-ID: <c868bce1-9a99-49d9-97cd-ead8d0295504@nvidia.com> (raw)
In-Reply-To: <87o7dswjry.wl-kuninori.morimoto.gx@renesas.com>
On 11-01-2024 10:26, Kuninori Morimoto wrote:
> External email: Use caution opening links or attachments
>
>
> Hi Sameer
>
>>>>> port {
>>>>> cpu_endpoint0: endpoint@0 { remote-endpoint = <&codec1_endpoint>; };
>>>>> cpu_endpoint1: endpoint@1 { remote-endpoint = <&codec2_endpoint>; };
>> You expect this endpoint to be exposed by driver right? Or are you
>> suggesting nothing needs to be done in the driver for this endpoint?
> If you use Card2, and if it is normal Codec (= not HDMI sound)
> basically you need is only DT settings, no driver patch is needed.
Is it possible to have similar behavior with audio-graph-card?
>>> Sample is for 2:3 connection, but it should be OK for 1:2.
>> For 1:N connection, how many DAI links audio-graph-card2 driver creates?
> DAI link max is based on ASoC.
> I think you want to know is connection N max. It is basically no limit
> on Card2
No, that is not what I am looking for. Let me please try to rephrase this.
Does audio-graph-card2 driver creates N+1 DAI links or a single DAI link?
next prev parent reply other threads:[~2024-01-11 5:10 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
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 [this message]
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=c868bce1-9a99-49d9-97cd-ead8d0295504@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