linux-kernel - Re: [RFC PATCH] ASoC: simple-card: Use dai

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAEnQRZAVM6=2udYg0jY8dD_uVE8yGQgsoZ14K1MBiCP+dCqLNQ@mail.gmail.com>
Date:   Wed, 22 Nov 2023 12:16:34 +0200
From:   Daniel Baluta <daniel.baluta@...il.com>
To:     Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>
Cc:     Daniel Baluta <daniel.baluta@....nxp.com>,
        "broonie@...nel.org" <broonie@...nel.org>,
        "alsa-devel@...a-project.org" <alsa-devel@...a-project.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "iuliana.prodan@....com" <iuliana.prodan@....com>,
        "shengjiu.wang@....com" <shengjiu.wang@....com>
Subject: Re: [RFC PATCH] ASoC: simple-card: Use dai_id from node description

On Wed, Nov 22, 2023 at 5:39 AM Kuninori Morimoto
<kuninori.morimoto.gx@...esas.com> wrote:
>
>
> Hi Daniel
>
> > > But hmm... in your case, you need to setup 2ports, and use 2nd port
> > > is assumed approach.
> > > Why you don't setup full port ? Do you have some reason ??
> (snip)
> > Now, I want to write a DTS description where my DAI link uses
> > Component 0 (CPU) (with its DAI index 1) connected with Component 1
> > (codec) (with its DAI index 0).
>
> Thank you for indicating your DTS.
>
> So in imx8m_dai case, it has total 3 DAIs, and you want to use reg = 1.
> In such case, your DTS need to have like below, if my understanding was
> correct.
>
>         dsp: dsp@...e8000 {
>                 ports {
>                              port@0 { reg = <0>;         endpoint { /* not used */ };  };
>                         cpu: port@1 { reg = <1>; cpu_ep: endpoint { remote-endpoint = <xxx>; }; };
>                              port@2 { reg = <2>;         endpoint { /* not used */ };  };
>                 };
>         };
>

This works! Thanks. I didn't know that you can leave an endpoint unused :).

So please ignore my initial patch then.