[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160329160703.GN2350@sirena.org.uk>
Date: Tue, 29 Mar 2016 09:07:03 -0700
From: Mark Brown <broonie@...nel.org>
To: PC Liao <pc.liao@...iatek.com>
Cc: "tiwai@...e.de" <tiwai@...e.de>,
srv_heupstream <srv_heupstream@...iatek.com>,
"linux-mediatek@...ts.infradead.org"
<linux-mediatek@...ts.infradead.org>,
"s.hauer@...gutronix.de" <s.hauer@...gutronix.de>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"alsa-devel@...a-project.org" <alsa-devel@...a-project.org>,
Koro Chen (陳思翰) <koro.chen@...iatek.com>
Subject: Re: [PATCH] ASoC: mediatek: Add second I2S on mt8173-rt5650 machine
driver
On Tue, Mar 29, 2016 at 09:28:23PM +0800, PC Liao wrote:
> - mediatek,rt5650_i2s: I2S mode of rt5650
> 0: Default setting. Playback and record path use same set of I2S.
> Playback/Record path using same I2S clock connect from MT8173 I2S1 to
> rt5650 I2S1.
> 1: Playback and record path use different set of I2S. Playback path
> connects from MT8173 I2S1 to rt5650 I2S1 and record path connects from
> MT8173 I2S2 to rt5650 I2S2.
> Because we use codec ASRC function and need to initialize on different
> setting about this parts:
This sort of arrangement is very common - it's often needed to get
different sample rates for playback and capture. Normally it'd be
represented in the DT by having the two DAI links specified normally and
then having the driver look at the DT to see what's connected to work
out what mode to use.
Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)
Powered by blists - more mailing lists