From: Mark Brown <broonie@sirena.org.uk>
To: Steve Sakoman <sakoman@gmail.com>
Cc: Jarkko Nikula <jarkko.nikula@nokia.com>,
alsa-devel@alsa-project.org, linux-omap@vger.kernel.org,
Steve Sakoman <steve@sakoman.com>
Subject: Re: [alsa-devel] [PATCH 3/5] SOUND: SOC: CODECS: Add support for the TWL4030 audio codec
Date: Fri, 5 Sep 2008 11:30:40 +0100 [thread overview]
Message-ID: <20080905103040.GD12383@sirena.org.uk> (raw)
In-Reply-To: <5e088bd90809040732x24b2123cl68fa9d2242ae2ae0@mail.gmail.com>
On Thu, Sep 04, 2008 at 07:32:28AM -0700, Steve Sakoman wrote:
> On Thu, Sep 4, 2008 at 3:26 AM, Jarkko Nikula <jarkko.nikula@nokia.com> wrote:
> >> +static void twl4030_dump_registers(void)
> >> +{
> > This is not needed since there is already nice function
> > for it: sound/soc/soc-core.c: codec_reg_show.
> I could probably get rid of this function. It was quite useful during
> debugging and I was not aware of codec_reg_show. IIRC, most of the
> other codec drivers also have the equivalent of this function, so we
> might want to clean them up too if there is a standard function to
> replace them.
Any references? None of the in-tree drivers have them...
> >> +static void twl4030_power_down(struct snd_soc_codec *codec)
> >> +{
> > ...
> >> + udelay(10);
> >> +}
> > REVISIT comment for these kind of magic delays if doesn't work without.
> It *seems* to work without them, but every historic TI driver seemed
> to have them. I figured that they might know something not reflected
> in the documentation. I will add a REVIST comment.
This sort of stuff is very common in codec drivers - normally the delays
are there to allow the analogue side of the system time to settle down
(waiting for capacitors to charge/discharge or reference voltages to
stabalise, for example). Ideally they have comments saying what's going
on, of course. Missing these delays often won't actually stop things
working completely but will instead do things like reduce performance or
generate audio artefacts - and sometimes it's application dependant if
these are important.
next prev parent reply other threads:[~2008-09-05 10:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-04 5:01 [PATCH 0/4] ARM: OMAP2: Add support for Gumstix Overo (resubmission) sakoman
2008-09-04 5:01 ` [PATCH 1/5] ARM: OMAP2: Add support for the Gumstix Overo board sakoman
2008-09-04 5:01 ` [PATCH 2/5] ARM: OMAP2: Add video driver " sakoman
2008-09-04 5:01 ` [PATCH 3/5] SOUND: SOC: CODECS: Add support for the TWL4030 audio codec sakoman
2008-09-04 5:01 ` [PATCH 4/5] SOUND: SOC: OMAP: Add support for Gumstix Overo sakoman
2008-09-04 5:02 ` [PATCH 5/5] ARM: OMAP2: defconfig for the Gumstix Overo board sakoman
2008-09-04 10:40 ` [PATCH 4/5] SOUND: SOC: OMAP: Add support for Gumstix Overo Jarkko Nikula
2008-09-04 13:12 ` Steve Sakoman
2008-09-04 12:27 ` [alsa-devel] " Mark Brown
2008-09-04 10:26 ` [PATCH 3/5] SOUND: SOC: CODECS: Add support for the TWL4030 audio codec Jarkko Nikula
2008-09-04 12:25 ` [alsa-devel] " Mark Brown
2008-09-04 12:40 ` REGISTER 2 PCM FOR SAME DEVICE dinesh
2008-09-04 14:32 ` [PATCH 3/5] SOUND: SOC: CODECS: Add support for the TWL4030 audio codec Steve Sakoman
2008-09-05 10:30 ` Mark Brown [this message]
2008-09-05 14:25 ` Steve Sakoman
2008-09-04 12:04 ` Mark Brown
2008-09-04 14:48 ` [alsa-devel] " Steve Sakoman
2008-09-05 10:06 ` Mark Brown
2008-09-05 14:16 ` Steve Sakoman
2008-09-05 14:34 ` Steve Sakoman
2008-09-05 14:48 ` Mark Brown
2008-09-05 15:08 ` 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=20080905103040.GD12383@sirena.org.uk \
--to=broonie@sirena.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=jarkko.nikula@nokia.com \
--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