From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pierre-Louis Bossart Subject: Re: [alsa-devel] [PATCH 00/10] mfd: Add support for Analog Devices A2B transceiver Date: Tue, 17 Dec 2019 13:29:20 -0600 Message-ID: References: <20191209183511.3576038-1-daniel@zonque.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20191209183511.3576038-1-daniel@zonque.org> Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org To: Daniel Mack , linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org, linux-i2c@vger.kernel.org, alsa-devel@alsa-project.org, devicetree@vger.kernel.org, linux-clk@vger.kernel.org Cc: lars@metafoo.de, sboyd@kernel.org, mturquette@baylibre.com, robh+dt@kernel.org, broonie@kernel.org, pascal.huerst@gmail.com, lee.jones@linaro.org List-Id: linux-i2c@vger.kernel.org > 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.