public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: olivier.moysan@st.com (Olivier MOYSAN)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 2/3] ASoC: stm32: Add I2S driver
Date: Mon, 22 May 2017 15:11:45 +0000	[thread overview]
Message-ID: <3b507e82-d8d1-c2c4-8a50-ca130382171a@st.com> (raw)
In-Reply-To: <20170519173359.277lyg6fzwksqnin@sirena.org.uk>

Hello Mark,

Thanks, for applying the patches.

On 05/19/2017 07:33 PM, Mark Brown wrote:
> On Thu, May 18, 2017 at 05:19:52PM +0200, olivier moysan wrote:
> 
> This looks good so I'm going to apply it, a few things below though -
> can you please send a followup patch for the issue with the Kconfig
> symbol?
> 
>> --- a/sound/soc/stm/Kconfig
>> +++ b/sound/soc/stm/Kconfig
>> @@ -5,4 +5,4 @@ menuconfig SND_SOC_STM32
>>   	select SND_SOC_GENERIC_DMAENGINE_PCM
>>   	select REGMAP_MMIO
>>   	help
>> -	  Say Y if you want to enable ASoC-support for STM32
>> +	  Say Y if you want to enable ASoC support for STM32
> 
> This appears to be an unrelated typo fix.
> 

ok

>> diff --git a/sound/soc/stm/Makefile b/sound/soc/stm/Makefile
>> index e466a47..8251931 100644
>> --- a/sound/soc/stm/Makefile
>> +++ b/sound/soc/stm/Makefile
>> @@ -4,3 +4,7 @@ obj-$(CONFIG_SND_SOC_STM32) += snd-soc-stm32-sai-sub.o
>>   
>>   snd-soc-stm32-sai-objs := stm32_sai.o
>>   obj-$(CONFIG_SND_SOC_STM32) += snd-soc-stm32-sai.o
>> +
>> +# I2S
>> +snd-soc-stm32-i2s-objs := stm32_i2s.o
>> +obj-$(CONFIG_SND_SOC_STM32) += snd-soc-stm32-i2s.o
> 
> Perhaps make this a separate option?  It probably makes sense to rename
> the option for the SAI at the same time.
> 

ok, I will fix it in a new patch.

>> +
>> +	ret = clk_prepare_enable(i2s->pclk);
>> +	if (ret) {
>> +		dev_err(&pdev->dev, "Enable pclk failed: %d\n", ret);
>> +		return ret;
>> +	}
>> +
>> +	ret = clk_prepare_enable(i2s->i2sclk);
>> +	if (ret) {
>> +		dev_err(&pdev->dev, "Enable i2sclk failed: %d\n", ret);
>> +		goto err_pclk_disable;
>> +	}
> 
> It'd be nice to have runtime PM to disable these when the device is idle
> but that's not essential.
> 

Yes, I agree.

BRs
olivier

  reply	other threads:[~2017-05-22 15:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-18 15:19 [PATCH v4 0/3] ASoC: Add STM32 I2S support olivier moysan
2017-05-18 15:19 ` [PATCH v4 1/3] dt-bindings: Document STM32 I2S bindings olivier moysan
2017-05-19 17:37   ` Applied "ASoC: stm32: Document STM32 I2S bindings" to the asoc tree Mark Brown
2017-05-23 14:26   ` [PATCH v4 1/3] dt-bindings: Document STM32 I2S bindings Rob Herring
2017-05-18 15:19 ` [PATCH v4 2/3] ASoC: stm32: Add I2S driver olivier moysan
2017-05-19 17:33   ` Mark Brown
2017-05-22 15:11     ` Olivier MOYSAN [this message]
2017-05-18 15:19 ` [PATCH v4 3/3] ASoC: stm32: Add full duplex support to i2s olivier moysan

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=3b507e82-d8d1-c2c4-8a50-ca130382171a@st.com \
    --to=olivier.moysan@st.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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