linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: pc.liao@mediatek.com (PC Liao)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ASoC: mediatek: Add second I2S on mt8173-rt5650 machine driver
Date: Fri, 1 Apr 2016 10:50:52 +0800	[thread overview]
Message-ID: <1459479052.24414.3.camel@mtksdaap41> (raw)
In-Reply-To: <20160329160703.GN2350@sirena.org.uk>

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!

  reply	other threads:[~2016-04-01  2:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-25  3:42 [PATCH] ASoC: mediatek: Add second I2S on mt8173-rt5650 machine driver PC Liao
2016-03-28 19:11 ` Mark Brown
2016-03-29 13:28   ` PC Liao
2016-03-29 16:07     ` Mark Brown
2016-04-01  2:50       ` PC Liao [this message]
2016-04-02 17:04         ` Mark Brown
2016-04-06 13:58           ` PC Liao
2016-04-06 17:17             ` Mark Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1459479052.24414.3.camel@mtksdaap41 \
    --to=pc.liao@mediatek.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).