From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Steve Sakoman <sakoman@gmail.com>
Cc: linux-omap@vger.kernel.org, alsa-devel@alsa-project.org,
Steve Sakoman <steve@sakoman.com>
Subject: Re: [alsa-devel] [PATCH 2/4] SOUND: SOC: CODECS: Add support for the TWL4030 audio codec
Date: Tue, 2 Sep 2008 15:53:28 +0100 [thread overview]
Message-ID: <20080902145328.GA3764@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <5e088bd90809020725g1d0dff70ue84f861ea3e22201@mail.gmail.com>
On Tue, Sep 02, 2008 at 07:25:48AM -0700, Steve Sakoman wrote:
> On Tue, Sep 2, 2008 at 4:26 AM, Mark Brown <broonie@sirena.org.uk> wrote:
> > This should also be added to SND_SOC_ALL_CODECS to ensure testing
> > coverage.
> Hmm . . . I get no hits grep-ing for SND_SOC_ALL_CODECS. Could this
> be something we are missing in the linux-omap git?
Yes, it's queued in ALSA for merge in the next window:
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-2.6.git
> >> +struct twl4030_priv {
> >> + unsigned int dummy;
> >> +};
> > If this is empty it should be removable?
> I plan to support further codec features in future patches and have a
> strong suspicion that private data may be required. Is it preferred
> to add the infrastructure now, or wait till it is required in the
> future? I opted for the former, but don't really care either way.
It'd be a bit cleaner to remove it but it's not a big deal either way -
leave it in if you find it useful.
> >> + twl4030_write(codec, REG_ARXL2PGA, 0x00);
> >> + twl4030_write(codec, REG_ARXR2PGA, 0x00);
> >> + twl4030_write_reg_cache(codec, REG_ARXL2PGA, ldac_reg);
> >> + twl4030_write_reg_cache(codec, REG_ARXR2PGA, rdac_reg);
> >> + } else {
> >> + twl4030_write(codec, REG_ARXL2PGA, ldac_reg);
> >> + twl4030_write(codec, REG_ARXR2PGA, rdac_reg);
> >> + }
> > It may be better to make these user visible controls - usually the mute
> > provided here is specifically for the DAC but these look like controls
> > for the PGA. The intention here is to avoid artifacts from the DAC when
> > the input clock stops and start - if there aren't any then user space
> > may well appreciate the control. Either way is fine.
> I'm not hearing any clicks & pops, so I will leave this in.
The point is that adding it in suppresses problems that might otherwise
occur - if it doesn't misbehave without this users may find it useful if
the mute control to be visible to them.
> >> + twl4030_init_chip();
> >> + twl4030_power_up(codec, APLL_RATE_44100 | OPT_MODE);
> > It looks like the driver is assuming a particular clock rate going into
> > the codec - does the chip require a fixed clock or is the driver only
> > supporting one configuration? Either is fine.
> There is a fixed clock.
Fixed per board or fixed by the chip?
next prev parent reply other threads:[~2008-09-02 14:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-01 21:57 [PATCH 0/4] ARM: OMAP2: Add support for Gumstix Overo sakoman
2008-09-01 21:57 ` [PATCH 1/4] ARM: OMAP2: Add support for the Gumstix Overo board sakoman
2008-09-01 21:57 ` [PATCH 2/4] SOUND: SOC: CODECS: Add support for the TWL4030 audio codec sakoman
2008-09-01 21:57 ` [PATCH 3/4] SOUND: SOC: OMAP: Add support for Gumstix Overo sakoman
2008-09-01 21:57 ` [PATCH 4/4] ARM: OMAP2: deconfig for the Gumstix Overo board sakoman
2008-09-02 11:29 ` [PATCH 3/4] SOUND: SOC: OMAP: Add support for Gumstix Overo Mark Brown
2008-09-02 13:19 ` Steve Sakoman
2008-09-02 11:26 ` [PATCH 2/4] SOUND: SOC: CODECS: Add support for the TWL4030 audio codec Mark Brown
2008-09-02 12:27 ` [alsa-devel] " Felipe Balbi
2008-09-02 14:25 ` Steve Sakoman
2008-09-02 14:53 ` Mark Brown [this message]
2008-09-02 16:36 ` Steve Sakoman
2008-09-02 18:54 ` [alsa-devel] " Mark Brown
2008-09-02 20:08 ` Liam Girdwood
2008-09-02 20:31 ` [alsa-devel] " Mark Brown
2008-09-02 20:51 ` Liam Girdwood
2008-09-02 20:48 ` [alsa-devel] " Steve Sakoman
2008-09-02 20:38 ` David Brownell
2008-09-02 0:46 ` [PATCH 1/4] ARM: OMAP2: Add support for the Gumstix Overo board Felipe Balbi
[not found] ` <200809020815.58792.david-b@pacbell.net>
2008-09-02 16:04 ` Steve Sakoman
2008-09-02 20:58 ` Russell King - ARM Linux
2008-09-02 21:06 ` Steve Sakoman
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=20080902145328.GA3764@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-omap@vger.kernel.org \
--cc=sakoman@gmail.com \
--cc=steve@sakoman.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