From mboxrd@z Thu Jan 1 00:00:00 1970 From: lee.jones@linaro.org (Lee Jones) Date: Wed, 6 Nov 2013 12:07:58 +0000 Subject: [PATCH 06/13] ASoC: ux500_pcm: Extend ux500 MSP binding for enumeration In-Reply-To: References: <1383732985-18928-1-git-send-email-lee.jones@linaro.org> <1383732985-18928-7-git-send-email-lee.jones@linaro.org> <20131106104658.GE11602@sirena.org.uk> Message-ID: <20131106120758.GG30901@lee--X1> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Wed, 06 Nov 2013, Linus Walleij wrote: > On Wed, Nov 6, 2013 at 11:46 AM, Mark Brown wrote: > > On Wed, Nov 06, 2013 at 10:16:18AM +0000, Lee Jones wrote: > > >> + - id : MSP ID - used during component registration > > > > I have no idea what this means or how one would pick the number? It > > looks like something purely internal to the driver... > > Actually it's quite common when we have several HW blocks of the > same thing to add something like an id. For example for different > GPIO banks. > > But in this case I guess it may make more sense to flag one MSP > for RX and one for TX or something? > > There are also two more such MSPs for streaming audio to the > Bluetooth audio portions. Right, we have 4 of them: MSP0: Tx and Rx MSP1: Tx MSP2: Tx and Rx MSP3: Rx -- Lee Jones Linaro STMicroelectronics Landing Team Lead Linaro.org ? Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog