From: Brian Austin <brian.austin@cirrus.com>
To: Dinh Nguyen <dinh.linux@gmail.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Brian Austin <brian.austin@cirrus.com>,
alsa-devel@alsa-project.org, Rob Herring <robh+dt@kernel.org>,
lgirdwood@gmail.com, broonie@kernel.org,
Kumar Gala <galak@codeaurora.org>
Subject: Re: [PATCH 1/2] ASoC: Add support for CS35L32 Boosted Amplifier
Date: Thu, 31 Jul 2014 09:37:38 -0500 [thread overview]
Message-ID: <alpine.DEB.2.02.1407310936000.7394@heelrod> (raw)
In-Reply-To: <CADhT+wfub5Li5tdM+dTnridOs9k5GwaKDTKvo7s-nefS4Oymyg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1810 bytes --]
On Wed, 30 Jul 2014, Dinh Nguyen wrote:
>
>
>
> On Tue, Jul 29, 2014 at 3:02 PM, Brian Austin <brian.austin@cirrus.com> wrote:
> This patch adds support for the Cirrus Logic CS35L32 Boosted Amplifier
> I2S Output provides monitor data to the SOC/CODEC for speaker protection algorithms
>
> Signed-off-by: Brian Austin <brian.austin@cirrus.com>
> ---
> include/dt-bindings/sound/cs35l32.h | 26 ++
> sound/soc/codecs/Kconfig | 5 +
> sound/soc/codecs/Makefile | 2 +
> sound/soc/codecs/cs35l32.c | 670 +++++++++++++++++++++++++++++++++++
> sound/soc/codecs/cs35l32.h | 97 +++++
> 5 files changed, 800 insertions(+)
> create mode 100644 include/dt-bindings/sound/cs35l32.h
> create mode 100644 sound/soc/codecs/cs35l32.c
> create mode 100644 sound/soc/codecs/cs35l32.h
>
> +
> +static int int_clear(struct snd_soc_dapm_widget *w,
> + struct snd_kcontrol *kcontrol, int event)
> +{
> + struct snd_soc_codec *codec = w->codec;
> +
> + if (SND_SOC_DAPM_EVENT_ON(event)) {
> + snd_soc_read(codec, CS35L32_INT_STATUS_1);
> + snd_soc_read(codec, CS35L32_INT_STATUS_2);
> + } else {
> + return 0;
> + }
> + return 0;
>
>
> Can remove one of the "return 0" or why not just a void?
You know, I think I am just going to remove this altogether. It was a
request from Apps and I don't think it is really needed. I'll test without
it and send a v2 with it removed.
Thanks,
Brian
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2014-07-31 14:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-29 20:02 [PATCH 1/2] ASoC: Add support for CS35L32 Boosted Amplifier Brian Austin
[not found] ` <1406664163-10506-1-git-send-email-brian.austin-jGc1dHjMKG3QT0dZR+AlfA@public.gmane.org>
2014-07-29 20:02 ` [PATCH 2/2] Documentation: dt: bindings: sound: Add bindings file for CS35L32 Brian Austin
[not found] ` <1406664163-10506-2-git-send-email-brian.austin-jGc1dHjMKG3QT0dZR+AlfA@public.gmane.org>
2014-07-31 20:21 ` Mark Brown
[not found] ` <20140731202149.GX17528-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-07-31 20:40 ` Brian Austin
2014-07-31 21:18 ` Mark Brown
[not found] ` <20140731211828.GA17528-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-07-31 21:28 ` Brian Austin
2014-07-31 20:07 ` [PATCH 1/2] ASoC: Add support for CS35L32 Boosted Amplifier Mark Brown
[not found] ` <20140731200729.GW17528-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-07-31 20:27 ` Brian Austin
2014-07-31 20:27 ` Mark Brown
2014-07-30 21:02 ` Dinh Nguyen
2014-07-31 14:37 ` Brian Austin [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=alpine.DEB.2.02.1407310936000.7394@heelrod \
--to=brian.austin@cirrus.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dinh.linux@gmail.com \
--cc=galak@codeaurora.org \
--cc=lgirdwood@gmail.com \
--cc=robh+dt@kernel.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