[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160607120647.GV7510@sirena.org.uk>
Date: Tue, 7 Jun 2016 13:06:47 +0100
From: Mark Brown <broonie@...nel.org>
To: Xing Zheng <zhengxing@...k-chips.com>
Cc: Rob Herring <robh@...nel.org>, linux-rockchip@...ts.infradead.org,
dianders@...omium.org, heiko@...ech.de,
Pawel Moll <pawel.moll@....com>,
Mark Rutland <mark.rutland@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Kumar Gala <galak@...eaurora.org>,
Liam Girdwood <lgirdwood@...il.com>,
Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.com>, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
alsa-devel@...a-project.org
Subject: Re: [PATCH v3] ASoC: rockchip: Add machine driver for
MAX98357A/RT5514/DA7219
On Tue, Jun 07, 2016 at 07:38:23PM +0800, Xing Zheng wrote:
> On 2016年06月07日 18:47, Mark Brown wrote:
> > No, that'd be one card with all three CODECs on the same board which I'm
> > guessing isn't the intention?
> Yes, because on our board, the audio connection by hardware really is such:
> |-- max98357a
> i2s0 <==> |-- rt5514
> | -- da7219
> We do need to support max98357a / rt5514 / da7219 via i2s0 on the same board
> for RK3399.
> I remember that it will be failed if we register card with i2s0 more times.
> Therefore, I chose this mothod that create 3 dai-links on one machine
> driver.
OK, then the original name probably makes some sense though really
that's such an unusual design that just naming it after the specific
board might be better, it's not likely to see any reuse I'd guess.
Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)
Powered by blists - more mailing lists