From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Kuninori Morimoto <morimoto.kuninori@renesas.com>
Cc: linux-sh@vger.kernel.org, alsa-devel@alsa-project.org,
Takashi Iwai <tiwai@suse.de>,
lethal@linux-sh.org, Magnus Damm <magnus.damm@gmail.com>
Subject: Re: [alsa-devel] [PATCH v2 2/4] Add ak464x codec support
Date: Thu, 20 Aug 2009 18:58:36 +0000 [thread overview]
Message-ID: <20090820185835.GE5032@sirena.org.uk> (raw)
In-Reply-To: <uws4yd793.wl%morimoto.kuninori@renesas.com>
On Thu, Aug 20, 2009 at 09:01:12PM +0900, Kuninori Morimoto wrote:
> This is very simple driver for ALSA
> It supprt headphone output and stereo input only
> This patch is tested by ms7724se
Thanks, this looks good but it needs updating for a recent change in the
current ASoC tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound-2.6.git for-2.6.32
sound/soc/codecs/ak4642.c: In function ‘ak4642_read’:
sound/soc/codecs/ak4642.c:130: warning: passing argument 2 of ‘codec->hw_read’ makes integer from pointer without a cast
sound/soc/codecs/ak4642.c:130: error: too many arguments to function ‘codec->hw_read’
sound/soc/codecs/ak4642.c: In function ‘ak4642_init’:
sound/soc/codecs/ak4642.c:332: warning: assignment from incompatible pointer type
Also, a couple of minor issues:
> +static const struct i2c_device_id ak4642_i2c_id[] = {
> + { "ak4642", 0 },
> + { }
> +};
Since the ak4643 is also supported you should add an entry for it to
this table.
> +struct ak4642_setup_data {
> + int i2c_bus;
> + unsigned short i2c_address;
> +};
This struct isn't used any more and so should be removed.
prev parent reply other threads:[~2009-08-20 18:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 12:01 [PATCH v2 2/4] Add ak464x codec support Kuninori Morimoto
2009-08-20 18:58 ` Mark Brown [this message]
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=20090820185835.GE5032@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lethal@linux-sh.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=morimoto.kuninori@renesas.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