From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Prchal Jiří" <jiri.prchal@aksignal.cz>
Cc: vbarinov@embeddedalley.com, alsa-devel@alsa-project.org,
sudhakar.raj@ti.com, nsekhar@ti.com, peter.ujfalusi@ti.com,
mr.swami.reddy@ti.com, lrg@ti.com
Subject: Re: [PATCH] ASoC: tlv320aic3x: add input clock selection
Date: Tue, 26 Jun 2012 11:26:28 +0100 [thread overview]
Message-ID: <20120626102627.GN30406@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4FE98D28.8050908@aksignal.cz>
[-- Attachment #1.1: Type: text/plain, Size: 838 bytes --]
On Tue, Jun 26, 2012 at 12:21:28PM +0200, Prchal Jiří wrote:
> + /* set clock on MCLK or GPIO2 or BCLK */
> + snd_soc_update_bits(codec, AIC3X_CLKGEN_CTRL_REG, PLLCLK_IN_MASK, clk_id);
> + snd_soc_update_bits(codec, AIC3X_CLKGEN_CTRL_REG, CLKDIV_IN_MASK, clk_id);
Normally it's possible to set these separately. Is there a reason why
they have to be the same (and if so why has the chip got separate
registers)?
> +#define PLLCLK_IN_MASK 0x30
> +#define CLKDIV_IN_MASK 0xc0
> +/* clock in source */
> +#define CLKIN_MCLK 0
> +#define CLKIN_GPIO2 1
> +#define CLKIN_BCLK 2
This doesn't look right - you use the clock source values directly above
but they need shifting to be used as if they're used directly they'll
always come out as zero. It'd also be better to have some bounds
checking on the values.
[-- 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-26 10:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-26 10:21 [PATCH] ASoC: tlv320aic3x: add input clock selection Prchal Jiří
2012-06-26 10:26 ` Mark Brown [this message]
2012-06-26 11:47 ` Prchal Jiří
-- strict thread matches above, loose matches on Subject: below --
2012-07-10 12:36 Jiri Prchal
2012-07-10 13:42 ` 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=20120626102627.GN30406@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=jiri.prchal@aksignal.cz \
--cc=lrg@ti.com \
--cc=mr.swami.reddy@ti.com \
--cc=nsekhar@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=sudhakar.raj@ti.com \
--cc=vbarinov@embeddedalley.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.