From: Mark Brown <broonie@kernel.org>
To: Oder Chiou <oder_chiou@realtek.com>
Cc: Bard Liao <bardliao@realtek.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
Flove <flove@realtek.com>
Subject: Re: [PATCH v2] ASoC: rt5645: Add codec driver
Date: Mon, 5 May 2014 12:51:21 -0700 [thread overview]
Message-ID: <20140505195121.GX22111@sirena.org.uk> (raw)
In-Reply-To: <7EB0DE829A537248AF2ED30C97D1269436CBBD@RTITMBSV03.realtek.com.tw>
[-- Attachment #1.1: Type: text/plain, Size: 1555 bytes --]
On Mon, May 05, 2014 at 11:15:24AM +0000, Oder Chiou wrote:
> > > + /* I2S2 function select */
> > > + SOC_SINGLE("I2S2 Func Switch", RT5645_GPIO_CTRL1, RT5645_I2S2_SEL_SFT,
> > > + 1, 1),
> > What functions is this switching?
> It is the pin share switch. The I2S data pins are the pin share to GPIO3/4/5/6.
> If we want to use the GPIO3/4/5/6, we need to set it. We will modify it using the
> platform data to set it.
Yes, please - this shouldn't be visible at runtime.
> > > + /* TDM */
> > > + SOC_ENUM("TDM Adc Slot0 1 Data", rt5645_tdm_adc_slot0_1_enum),
> > > + SOC_ENUM("TDM Adc Slot2 3 Data", rt5645_tdm_adc_slot2_3_enum),
> > > + SOC_ENUM("TDM Adc Slot4 5 Data", rt5645_tdm_adc_slot4_5_enum),
> > > + SOC_ENUM("TDM Adc Slot6 7 Data", rt5645_tdm_adc_slot6_7_enum),
> > > + SOC_ENUM("TDM IF1 ADC DATA Sel", rt5645_tdm_adc_sel_enum),
> > > + SOC_SINGLE("TDM IF1_DAC1_L Sel", RT5645_TDM_CTRL_3, 12, 7, 0),
> > > + SOC_SINGLE("TDM IF1_DAC1_R Sel", RT5645_TDM_CTRL_3, 8, 7, 0),
> > > + SOC_SINGLE("TDM IF1_DAC2_L Sel", RT5645_TDM_CTRL_3, 4, 7, 0),
> > > + SOC_SINGLE("TDM IF1_DAC2_R Sel", RT5645_TDM_CTRL_3, 0, 7, 0),
> > These look like they should be part of DAPM, they're about routing data as far as I
> > can tell.
> These are the data related controls with TDM function, not related the routing path.
> For instance, it likes the L and R channel data swap, or copy function.
These are very much routing controls - the routing operates at a mono
level. Doing a left/right swap or stereo duplication of a mono control
is a routing thing.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2014-05-06 0:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 11:59 [PATCH v2] ASoC: rt5645: Add codec driver Oder Chiou
2014-05-03 17:42 ` Mark Brown
2014-05-05 11:15 ` Oder Chiou
2014-05-05 19:51 ` Mark Brown [this message]
2014-05-08 3:29 ` Oder
2014-05-08 5:20 ` 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=20140505195121.GX22111@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bardliao@realtek.com \
--cc=flove@realtek.com \
--cc=lgirdwood@gmail.com \
--cc=oder_chiou@realtek.com \
/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