From: Mark Brown <broonie@kernel.org>
To: Jean-Francois Moine <moinejf@free.fr>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.de>,
Rob Herring <rob.herring@calxeda.com>,
Russell King <rmk+kernel@arm.linux.org.uk>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 4/4] ASoc: kirkwood: add DT support
Date: Thu, 25 Jul 2013 20:19:05 +0100 [thread overview]
Message-ID: <20130725191905.GR9858@sirena.org.uk> (raw)
In-Reply-To: <20130725111459.145a4aa4@armhf>
[-- Attachment #1: Type: text/plain, Size: 898 bytes --]
On Thu, Jul 25, 2013 at 11:14:59AM +0200, Jean-Francois Moine wrote:
> + if (np) {
> + priv->burst = 128; /* might be 32 or 128 */
> + } else if (data) {
When you posted this before I queried how and why the value might vary -
I see the code is the same and I don't recall a reply.
> - priv->clk = devm_clk_get(&pdev->dev, NULL);
> + priv->clk = devm_clk_get(&pdev->dev, "internal");
> if (IS_ERR(priv->clk)) {
> - dev_err(&pdev->dev, "no clock\n");
> + dev_err(&pdev->dev, "no internal clock\n");
> return PTR_ERR(priv->clk);
> }
Does the code providing it already name the clock? If not are updates
needed to do that?
> - priv->extclk = clk_get(&pdev->dev, "extclk");
> + priv->extclk = clk_get(&pdev->dev, "external");
Is the clock actually called extclk in the datasheet and so on? If so
it seems better to stick with that name. Do any boards need updates for
the new name?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-07-25 19:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-25 9:14 [PATCH 4/4] ASoc: kirkwood: add DT support Jean-Francois Moine
2013-07-25 19:19 ` Mark Brown [this message]
2013-07-25 23:05 ` Russell King - ARM Linux
2013-07-26 9:09 ` Jean-Francois Moine
2013-07-26 9:21 ` Russell King - ARM Linux
2013-07-26 9:49 ` Jean-Francois Moine
2013-07-26 11:05 ` 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=20130725191905.GR9858@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=devicetree@vger.kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=moinejf@free.fr \
--cc=perex@perex.cz \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=rob.herring@calxeda.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