[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87ftv33bpg.wl-kuninori.morimoto.gx@renesas.com>
Date: Tue, 11 Dec 2018 23:16:33 +0000
From: Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>
To: Tony Lindgren <tony@...mide.com>
CC: Mark Brown <broonie@...nel.org>,
Liam Girdwood <lgirdwood@...il.com>,
Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.com>,
"alsa-devel@...a-project.org" <alsa-devel@...a-project.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>,
Sebastian Reichel <sre@...nel.org>,
Jarkko Nikula <jarkko.nikula@...mer.com>,
Peter Ujfalusi <peter.ujfalusi@...com>
Subject: Re: [PATCH 0/2] Graph fixes for using multiple endpoints per port
Hi Tony
> The issue I have with that it does not then follow the binding doc :)
>
> See this part in Documentation/devicetree/bindings/graph.txt:
>
> "If a single port is connected to more than one remote device, an
> 'endpoint' child node must be provided for each link."
>
> Isn't the I2C TDM case the same as "single port connecected to
> more than one remote device" rather than multiple ports?
>
> To me it seems we're currently only handling the multiple ports
> case, and not multiple endpoints for a port. Other than fixing
> that, things should work just as earlier with my two patches.
> That is unless I accidentally broke something.
>
> So just trying to correct the binding usage. Or am I missing
> something?
I'm not 100% sure your "I2C TDM case", but you can check
multi-endpoint sample on "Example: Multi DAI with DPCM" below.
"pcm3168a" is using multi-endpoint.
Does this help you ?
https://patchwork.kernel.org/patch/10712877/
Best regards
---
Kuninori Morimoto
Powered by blists - more mailing lists