From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Ola Lilja <ola.o.lilja@stericsson.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Liam Girdwood <lrg@ti.com>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH 2/3] ASoC: Ux500: Add machine-driver
Date: Mon, 11 Jun 2012 20:27:57 +0800 [thread overview]
Message-ID: <20120611122755.GQ11439@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4FD5E309.4080301@stericsson.com>
[-- Attachment #1.1: Type: text/plain, Size: 1575 bytes --]
On Mon, Jun 11, 2012 at 02:22:33PM +0200, Ola Lilja wrote:
> >> +static inline const char *get_mclk_str(enum mclk mclk_sel)
> >> +{
> >> + switch (mclk_sel) {
> >> + case MCLK_SYSCLK:
> >> + return "MCLK_SYSCLK";
> >> + case MCLK_ULPCLK:
> >> + return "MCLK_ULPCLK";
> > Why not just drop the MCLK_ from the strings? I'd expect that'll be
> > implied by the context...
> I like having some kind of prefix before the alternatives in my enums,
> even if you could figure out what its for without it.
Is the control name not enough for that? I'm only suggesting this for
the strings...
> >> + /* Digital interface - Clocks */
> >> + SOC_SINGLE("Digital Interface Master Generator Switch",
> >> + AB8500_DIGIFCONF1, AB8500_DIGIFCONF1_ENMASTGEN,
> >> + 1, 0),
> > This enables and disables a 256fs (or similar ratio) clock output from
> > the device?
> This is the clocking of the digital interface which is used together with the
> bit-clock switches when we are in gated mode (see discussions regarding these
> parameters in earlier review of the codec-driver).
> >> + SOC_SINGLE("Digital Interface 0 Bit-clock Switch",
> >> + AB8500_DIGIFCONF1, AB8500_DIGIFCONF1_ENFSBITCLK0,
> >> + 1, 0),
> >> + SOC_SINGLE("Digital Interface 1 Bit-clock Switch",
> >> + AB8500_DIGIFCONF1, AB8500_DIGIFCONF1_ENFSBITCLK1,
> >> + 1, 0),
> > I suspect that these are doing what DAIFMT_CONT is for...
> See comment above.
Can you refresh my memory on this discussion please? There's been
several occasions where I've been waiting for new code to make unclear
things clearer.
[-- 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:[~2012-06-11 12:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-07 12:00 [PATCH 2/3] ASoC: Ux500: Add machine-driver Ola Lilja
2012-06-11 5:34 ` Mark Brown
2012-06-11 12:22 ` Ola Lilja
2012-06-11 12:27 ` Mark Brown [this message]
2012-06-11 12:35 ` Ola Lilja
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=20120611122755.GQ11439@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=linus.walleij@linaro.org \
--cc=lrg@ti.com \
--cc=ola.o.lilja@stericsson.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.