[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cb86a793-014a-1acf-c144-f9014ac0a0ac@linux.intel.com>
Date: Tue, 17 Dec 2019 13:29:20 -0600
From: Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>
To: Daniel Mack <daniel@...que.org>, linux-kernel@...r.kernel.org,
linux-gpio@...r.kernel.org, linux-i2c@...r.kernel.org,
alsa-devel@...a-project.org, devicetree@...r.kernel.org,
linux-clk@...r.kernel.org
Cc: lars@...afoo.de, sboyd@...nel.org, mturquette@...libre.com,
robh+dt@...nel.org, broonie@...nel.org, pascal.huerst@...il.com,
lee.jones@...aro.org
Subject: Re: [alsa-devel] [PATCH 00/10] mfd: Add support for Analog Devices
A2B transceiver
> Transceivers can both receive and provide audio, and streams can be
> routed from one node to any other, including many others. The tricky
> bit is how to expose the audio routing in DT in a sane way.
> The way it is implemented here, the slave nodes specify the number of
> slots they each consume and generate, and which thereof they forward
> from one side to the other. This mimics the internal register
> structure and should allow for even exotic setups.
It was my understanding that the A2B bus is bidirectional but with
separate time windows allocated for host->device and device->host
transmission. The wording seems to hint at device-to-device
communication but I wonder if this is really what you meant.
Powered by blists - more mailing lists