[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdZgi9Egvm585Y9tJpmj0YX-oJBDg-C7pCu91Pf5ALMGLg@mail.gmail.com>
Date: Wed, 6 Nov 2013 12:55:51 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: Mark Brown <broonie@...nel.org>
Cc: Lee Jones <lee.jones@...aro.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>
Subject: Re: [PATCH 06/13] ASoC: ux500_pcm: Extend ux500 MSP binding for enumeration
On Wed, Nov 6, 2013 at 11:46 AM, Mark Brown <broonie@...nel.org> 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.
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists