From: Cyrille Pitchen <cyrille.pitchen@atmel.com>
To: Lars-Peter Clausen <lars@metafoo.de>, <lgirdwood@gmail.com>,
<broonie@kernel.org>, <perex@perex.cz>, <tiwai@suse.com>
Cc: <alsa-devel@alsa-project.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] ASoC: ad193x: add support to ad1934
Date: Tue, 29 Sep 2015 14:00:52 +0200 [thread overview]
Message-ID: <560A7D74.2090901@atmel.com> (raw)
In-Reply-To: <560A4EF7.9030506@metafoo.de>
Hi!
I'll fix it in v2. Thanks for your review!
Cyrille
Le 29/09/2015 10:42, Lars-Peter Clausen a écrit :
> On 09/29/2015 10:36 AM, Cyrille Pitchen wrote:
>> The AD1934 codec has no DAC feature. Hence it register mapping is slightly
>> different from the register mapping of other members of the AD193x family.
>>
>> Some ASoC controls and widgets are related to the DAC feature so are not
>> relevant in the case of an AD1934 codec.
>
> Looks mostly good, thanks.
>
>> diff --git a/sound/soc/codecs/ad193x-i2c.c b/sound/soc/codecs/ad193x-i2c.c
>> index df3a1a415825..8aa50d35662f 100644
>> --- a/sound/soc/codecs/ad193x-i2c.c
>> +++ b/sound/soc/codecs/ad193x-i2c.c
>> @@ -15,8 +15,8 @@
>> #include "ad193x.h"
>>
>> static const struct i2c_device_id ad193x_id[] = {
>> - { "ad1936", 0 },
>> - { "ad1937", 0 },
>> + { "ad1936", AD193x },
>> + { "ad1937", AD193x },
>
> Should be a upper case X.
>
>> { }
>> };
> [...]
> [...]
>> @@ -91,18 +97,33 @@ static const struct snd_soc_dapm_route audio_paths[] = {
>> { "DAC", NULL, "SYSCLK" },
>> { "DAC Output", NULL, "DAC" },
>> { "DAC Output", NULL, "VMID" },
>> - { "ADC", NULL, "SYSCLK" },
>> - { "DAC", NULL, "ADC_PWR" },
>> - { "ADC", NULL, "ADC_PWR" },
>> { "DAC1OUT", NULL, "DAC Output" },
>> { "DAC2OUT", NULL, "DAC Output" },
>> { "DAC3OUT", NULL, "DAC Output" },
>> { "DAC4OUT", NULL, "DAC Output" },
>> + { "SYSCLK", NULL, "PLL_PWR" },
>> +};
>> +
>> +static const struct snd_soc_dapm_route adc_audio_paths[] = {
>
> this should have the ad193x_ prefix as well.
>
>> + { "ADC", NULL, "SYSCLK" },
>> + { "ADC", NULL, "ADC_PWR" },
>> { "ADC", NULL, "ADC1IN" },
>> { "ADC", NULL, "ADC2IN" },
>> - { "SYSCLK", NULL, "PLL_PWR" },
>> };
>
prev parent reply other threads:[~2015-09-29 12:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 8:36 [PATCH 1/1] ASoC: ad193x: add support to ad1934 Cyrille Pitchen
2015-09-29 8:42 ` Lars-Peter Clausen
2015-09-29 12:00 ` Cyrille Pitchen [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=560A7D74.2090901@atmel.com \
--to=cyrille.pitchen@atmel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.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