From: Mark Brown <broonie@kernel.org>
To: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>,
Stephen Barber <smbarber@chromium.org>,
Mac Chiang <mac.chiang@intel.com>,
Ezequiel Garcia <ezequiel@collabora.co.uk>,
kernel@collabora.com
Subject: Re: [PATCH] ASoC: max98357a: Fix speaker pop when starting playback
Date: Thu, 22 Mar 2018 09:54:56 +0800 [thread overview]
Message-ID: <20180322015456.GZ2186@sirena.org.uk> (raw)
In-Reply-To: <20180321223015.32173-1-ezequiel@vanguardiasur.com.ar>
[-- Attachment #1.1: Type: text/plain, Size: 1172 bytes --]
On Wed, Mar 21, 2018 at 07:30:15PM -0300, Ezequiel Garcia wrote:
> +- sdmode-delay : specify a delay time for SD_MODE pin. According
> + to the DAC datasheet, if LRCLK is removed while BCLK is present,
> + the DAC output can cause loud pop/crack noises. This property
> + specifies a delay for the SD_MODE pin assert, required to
> + eliminate the noise.
Why is this configurable? This sounds like something entirely within
the digital domain of the device rather than something that depends on
board configuration and it's hard to see how someone would configure
this.
> +static void max98357a_enable_sdmode_work(struct work_struct *work)
> +{
> + struct max98357a_priv *max98357a = container_of(work,
> + struct max98357a_priv, enable_sdmode_work.work);
> + unsigned long flags;
> +
> + spin_lock_irqsave(&max98357a->sdmode_lock, flags);
> + gpiod_set_value(max98357a->sdmode, max98357a->sdmode_enabled);
> + spin_unlock_irqrestore(&max98357a->sdmode_lock, flags);
> +}
What is this lock supposed to accomplish? We perform a single action
under the lock which itself has internal locking, it's not going to have
any meaningful effect.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2018-03-22 1:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 22:30 [PATCH] ASoC: max98357a: Fix speaker pop when starting playback Ezequiel Garcia
2018-03-22 1:54 ` Mark Brown [this message]
2018-03-22 4:00 ` Ezequiel Garcia
2018-03-22 13:01 ` Ezequiel Garcia
2018-03-27 11:36 ` Mark Brown
2018-03-27 18:11 ` Ezequiel Garcia
2018-03-27 21:57 ` Ezequiel Garcia
2018-04-16 18:06 ` Mark Brown
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=20180322015456.GZ2186@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=ezequiel@collabora.co.uk \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=kernel@collabora.com \
--cc=lgirdwood@gmail.com \
--cc=mac.chiang@intel.com \
--cc=smbarber@chromium.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;
as well as URLs for NNTP newsgroup(s).