From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758171AbcDACvY (ORCPT ); Thu, 31 Mar 2016 22:51:24 -0400 Received: from mailgw02.mediatek.com ([210.61.82.184]:43169 "EHLO mailgw02.mediatek.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1753477AbcDACvW (ORCPT ); Thu, 31 Mar 2016 22:51:22 -0400 Message-ID: <1459479052.24414.3.camel@mtksdaap41> Subject: Re: [PATCH] ASoC: mediatek: Add second I2S on mt8173-rt5650 machine driver From: PC Liao To: Mark Brown CC: "tiwai@suse.de" , srv_heupstream , "linux-mediatek@lists.infradead.org" , "s.hauer@pengutronix.de" , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , "alsa-devel@alsa-project.org" , "Koro Chen =?UTF-8?Q?=28=E9=99=B3=E6=80=9D=E7=BF=B0=29?=" Date: Fri, 1 Apr 2016 10:50:52 +0800 In-Reply-To: <20160329160703.GN2350@sirena.org.uk> References: <1458877325-33980-1-git-send-email-pc.liao@mediatek.com> <20160328191115.GE2350@sirena.org.uk> <1459258103.3747.7.camel@mtksdaap41> <20160329160703.GN2350@sirena.org.uk> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.2.3-0ubuntu6 Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-MTK: N Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Mark, On Wed, 2016-03-30 at 00:07 +0800, Mark Brown wrote: > 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. Could you please suggest the reference driver about this? Thanks!