From: "Bryan Wu" <cooloney@kernel.org>
To: "Bryan Wu" <cooloney@kernel.org>,
perex@perex.cz, lrg@kernel.org,
"Cliff Cai" <cliff.cai@analog.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [alsa-devel] [PATCH 2/4] ASOC codec: add support for SSM2602 audio codec in ALSA SoC framework
Date: Thu, 28 Aug 2008 13:55:33 +0800 [thread overview]
Message-ID: <386072610808272255o7ef18860u29e10727e6e11a11@mail.gmail.com> (raw)
In-Reply-To: <20080827105456.GA10834@sirena.org.uk>
On Wed, Aug 27, 2008 at 6:54 PM, Mark Brown <broonie@sirena.org.uk> wrote:
> On Wed, Aug 27, 2008 at 05:39:26PM +0800, Bryan Wu wrote:
>
> This looks basically good, thanks - I've picked up a few things below
> but they are mostly either minor or reflect the fact that the patch
> looks like it's been developed against current release kernels but
> there's been some churn recently in the ASoC APIs which need updates.
>
>> #define I2C_DRIVERID_CS5345 96 /* cs5345 audio processor */
>> +#define I2C_DRIVERID_SSM2602 97 /* BF52xC built in audio codec */
>
> It should be possible to just remove this - it shouldn't be needed.
>
OK, I'll take care of this i2c stuff here.
>> --- a/sound/soc/codecs/Kconfig
>> +++ b/sound/soc/codecs/Kconfig
>
> Current kernels have a Kconfig option SND_SOC_ALL_CODECS which should
> have your codec added - this allows codec drivers to be built without
> boards for test purposes.
>
Is this option in alsa git tree or in the mainline? I fail to find it
in upstream mainline.
And do you mean I don't need to add SND_SOC_SSM2602 at all?
>> +#define SSM2602_DEBUG 0
>> +
>> +#ifdef SSM2602_DEBUG
>> +#define dbg(format, arg...) \
>> + printk(KERN_DEBUG AUDIO_NAME ": " format "\n" , ## arg)
>> +#else
>> +#define dbg(format, arg...) do {} while (0)
>> +#endif
>> +#define err(format, arg...) \
>> + printk(KERN_ERR AUDIO_NAME ": " format "\n" , ## arg)
>> +#define info(format, arg...) \
>> + printk(KERN_INFO AUDIO_NAME ": " format "\n" , ## arg)
>> +#define warn(format, arg...) \
>> + printk(KERN_WARNING AUDIO_NAME ": " format "\n" , ## arg)
>
> Please convert these to use the standard pr_ macros (or ideally the dev_
> ones where possible) for debug prints.
>
Right, I killed this local definition and replaced them to pr_xxxx.
>> +
>> +#define ssm2602_reset(c) ssm2602_write(c, SSM2602_RESET, 0)
>> +/*Appending several "None"s just for OSS mixer use*/
>> +static const char *ssm2602_input_select[] = {"Line", "Mic", "None", "None", "None",
>> + "None", "None", "None"};
>> +static const char *ssm2602_deemph[] = {"None", "32Khz", "44.1Khz", "48Khz"};
>
> Please keep the lines under 80 characters where reasonable. A little
> more while space (blank lines and at the start and end of comments)
> would be nice too.
>
Yes, I will fix this issue by running checkpatch.pl. And for other API
conflicts and I2C interface upgrading stuffs,
I will leave them to Cliff.
Thanks
-Bryan
next prev parent reply other threads:[~2008-08-28 5:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-27 9:39 [PATCH 0/4] Blackfin supports for ALSA/ASOC Bryan Wu
2008-08-27 9:39 ` [PATCH 1/4] ASOC: Blackfin driver for ALSA SoC framework Bryan Wu
2008-08-27 13:48 ` Mark Brown
2008-09-03 4:09 ` Cai, Cliff
2008-09-03 10:38 ` Mark Brown
2008-09-04 3:54 ` [alsa-devel] " Cliff Cai
2008-08-27 9:39 ` [PATCH 2/4] ASOC codec: add support for SSM2602 audio codec in " Bryan Wu
2008-08-27 10:54 ` [alsa-devel] " Mark Brown
2008-08-28 5:55 ` Bryan Wu [this message]
2008-08-28 10:06 ` Mark Brown
2008-08-28 11:44 ` Jean Delvare
2008-08-27 9:39 ` [PATCH 3/4] ASOC: WM8731 codec: add SPI support as well as I2C Bryan Wu
2008-08-27 11:01 ` [alsa-devel] " Mark Brown
2008-08-28 3:46 ` Bryan Wu
2008-08-28 10:14 ` Mark Brown
2008-08-28 12:47 ` Takashi Iwai
2008-08-28 13:01 ` Mark Brown
2008-09-01 13:52 ` Alan Horstmann
2008-09-01 14:00 ` Liam Girdwood
2008-09-01 14:02 ` Mark Brown
2008-08-27 9:39 ` [PATCH 4/4] ALSA: add dummy function to support shared mmap in nommu Blackfin arch Bryan Wu
2008-08-28 12:44 ` Takashi Iwai
2008-09-02 3:16 ` Cai, Cliff
2008-09-02 9:41 ` Takashi Iwai
2008-09-02 9:59 ` Bryan Wu
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=386072610808272255o7ef18860u29e10727e6e11a11@mail.gmail.com \
--to=cooloney@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=cliff.cai@analog.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@kernel.org \
--cc=perex@perex.cz \
/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
Powered by JetHome