From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Prchal Jiří" <jiri.prchal@aksignal.cz>
Cc: alsa-devel@vger.kernel.org, alsa-devel@alsa-project.org,
vbarinov@embeddedalley.com, linux-kernel@vger.kernel.org
Subject: Re: [alsa-devel] [PATCH 1/2] ALSA: ASoc: TLV320AIC3X: ad SPI and clock on GPIO2 or BCLK
Date: Mon, 4 Apr 2011 09:03:19 +0100 [thread overview]
Message-ID: <20110404080319.GA22584@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4D99781D.3030807@aksignal.cz>
On Mon, Apr 04, 2011 at 09:49:49AM +0200, Prchal Jiří wrote:
> Dne 2.4.2011 10:26, Mark Brown napsal(a):
> >> TODO: Set the model in SPI probe the right way. I don't know how.
> > Register two SPI drivers with different names.
> ???
Register a SPI driver per model.
> > This looks mostly good but there's some cleanups needed, mostly from
> > extra stuff which snuck in there, and you need to rebase against current
> > code.
> What cleanup? I copy functions snd_soc_8_8_* and made change to 7_8.
The comments I've made in the rest of the review such as removing random
whitespace updates.
> > As covered in SubmittingPatches you should always CC maintainers on
> > patches.
> Who is maintainer? I didn't find anyone, so I CC to author.
Myself and Liam Girdwood. At the most basic level the people you'd
expect to apply the patch.
> >> + /* set external clock on GPIO2 or BCLK */
> >> + data = snd_soc_read(codec, AIC3X_CLKGEN_CTRL_REG);
> >> + data &= 0x0f;
> >> + data |= ((clk_id << PLLCLK_IN_SHIFT) | (clk_id << CLKDIV_IN_SHIFT));
> >> + snd_soc_write(codec, AIC3X_CLKGEN_CTRL_REG, data);
> > This looks like an unrelated change which is specific to your board.
> > You should add an interface for configuring this functionality .
> No, it's for all, who uses other clock source. Interface is standard function:
> /* Set the codec system clock for DAC and ADC */
> ret = snd_soc_dai_set_sysclk(codec_dai,
> CLKIN_BCLK, cdu_audio[i].codecclk,
> SND_SOC_CLOCK_IN);
In that case you should submit a separate patch adding this
functionality, taking care to ensure that you don't break existing
users.
> >> +static struct spi_driver aic3x_spi_driver = {
> >> + .driver = {
> >> + .name = "tlv320aic3x-codec",
> >> + .owner = THIS_MODULE,
> > Remove the -codec from the driver name.
> Why? In I2C part it must be there, so should it be same?
No, it should be removed from the I2C driver too.
next prev parent reply other threads:[~2011-04-04 8:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1300949648-15078-1-git-send-email-horms@verge.net.au>
[not found] ` <1300949648-15078-2-git-send-email-horms@verge.net.au>
2011-03-24 10:20 ` [PATCH 1/2] ALSA: ASoc: TLV320AIC3X: ad SPI and clock on GPIO2 or BCLK Prchal Jiří
2011-04-02 8:26 ` Mark Brown
2011-04-04 7:49 ` [alsa-devel] " Prchal Jiří
2011-04-04 8:03 ` Mark Brown [this message]
2011-04-04 8:01 ` [PATCH] ALSA: ASoc: new functions snd_soc_7_8_* Prchal Jiří
2011-04-04 8:05 ` Mark Brown
2011-03-24 10:43 ` [PATCH 2/2] ALSA: ASoc: putting together AT91SAM9260 and TLV320AIC3X Prchal Jiří
2011-03-24 20:07 ` Ryan Mallon
2011-04-04 8:57 ` Prchal Jiří
2011-04-04 20:07 ` Ryan Mallon
2011-05-31 13:05 ` PROBLEM: ARM: PCM plugin Ima-ADPCM doesn't work properly Prchal Jiří
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=20110404080319.GA22584@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=alsa-devel@vger.kernel.org \
--cc=jiri.prchal@aksignal.cz \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).