From: Mark Brown <broonie@kernel.org>
To: Rongjun Ying <Rongjun.Ying@csr.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Takashi Iwai <tiwai@suse.de>,
DL-SHA-WorkGroupLinux <DL-SHA-WorkGroupLinux@internal.csr.com>,
Liam Girdwood <lgirdwood@gmail.com>,
RongJun Ying <rjying@gmail.com>
Subject: Re: [PATCH v4-resend 1/7] ASoC: sirf: Add SiRF internal audio codec driver
Date: Sat, 1 Mar 2014 12:16:46 +0900 [thread overview]
Message-ID: <20140301031646.GJ29849@sirena.org.uk> (raw)
In-Reply-To: <86130EF012BDF348AA0D464A4F449478012AE51755@SHAASIEXM01.ASIA.ROOT.PRI>
[-- Attachment #1.1: Type: text/plain, Size: 1378 bytes --]
On Fri, Feb 28, 2014 at 01:52:32AM +0000, Rongjun Ying wrote:
> > > +static struct sirf_audio_codec_reg_bits
> > sirf_audio_codec_reg_bits_prima2 = {
> > > + .dig_mic_en_bits = 20,
> > > + .dig_mic_freq_bits = 21,
> > This looks like the sort of thing that the regmap_field layer was
> > supposed to hide?
> Do you mean I need use the regmap_field_read/write to hide these?
You should certainly consider it and if it's not a good approach
understanding why may help us improve that API.
> > > +static int sirf_audio_codec_runtime_suspend(struct device *dev) {
> > > + struct sirf_audio_codec *sirf_audio_codec = dev_get_drvdata(dev);
> > > + regmap_update_bits(sirf_audio_codec->regmap, AUDIO_IC_CODEC_CTRL1,
> > > + (1 << sirf_audio_codec->reg_bits->codec_clk_en_bits),
> > > + 0);
> > > + return 0;
> > > +}
> > Can you disable the clock in the clock API as well? This might allow
> > further supply clocks to be disabled and is genarally good practice.
> This is a workaround. The capture ADC and touch ADC use a same power supply,
> The codec ADC's change pump set or clear will impact touch ADC unstable.
> So It's need enable codec clock and set change pump when the Audio driver init.
That doesn't really answer the question for me - I wasn't asking why the
clock was being disabled, I was asking why the disable wasn't also being
done at the clock API level.
[-- 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-03-01 3:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 7:22 [PATCH v4-resend 0/7] ASoC: add CSR SiRFSoC sound drivers RongJun Ying
2014-02-26 7:22 ` [PATCH v4-resend 1/7] ASoC: sirf: Add SiRF internal audio codec driver RongJun Ying
2014-02-27 5:33 ` Mark Brown
2014-02-28 1:52 ` Rongjun Ying
2014-03-01 3:16 ` Mark Brown [this message]
2014-03-03 2:15 ` Rongjun Ying
2014-03-03 5:07 ` Mark Brown
2014-03-03 7:48 ` Barry Song
2014-03-04 4:58 ` Mark Brown
2014-03-04 5:11 ` RongJun Ying
2014-03-05 3:34 ` Mark Brown
2014-03-05 5:34 ` RongJun Ying
2014-02-26 7:22 ` [PATCH v4-resend 2/7] ASoC: sirf: Add SiRF audio port driver is used by SiRF internal audio codec RongJun Ying
2014-03-01 4:49 ` Mark Brown
2014-02-26 7:22 ` [PATCH v4-resend 3/7] ASoC: sirf: Add SiRF audio card RongJun Ying
2014-02-26 7:22 ` [PATCH v4-resend 4/7] ASoC: sirf: Add SiRF I2S driver RongJun Ying
2014-02-26 7:22 ` [PATCH v4-resend 5/7] ASoC: sirf: Add hdmi card RongJun Ying
2014-02-26 7:22 ` [PATCH v4-resend 6/7] ASoC: sirf: Add usp driver which is used by dsp mode RongJun Ying
2014-02-26 7:22 ` [PATCH v4-resend 7/7] ASoC: sirf: Add bt-sco card RongJun Ying
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=20140301031646.GJ29849@sirena.org.uk \
--to=broonie@kernel.org \
--cc=DL-SHA-WorkGroupLinux@internal.csr.com \
--cc=Rongjun.Ying@csr.com \
--cc=alsa-devel@alsa-project.org \
--cc=lgirdwood@gmail.com \
--cc=rjying@gmail.com \
--cc=tiwai@suse.de \
/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