From: Alper Nebi Yasak <alpernebiyasak@gmail.com>
To: Tzung-Bi Shih <tzungbi@google.com>
Cc: Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Heiko Stuebner <heiko@sntech.de>,
ALSA development <alsa-devel@alsa-project.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-rockchip@lists.infradead.org
Subject: Re: Speaker pops with max98357a on rk3399-gru-kevin since v5.7
Date: Tue, 21 Jul 2020 01:40:14 +0300 [thread overview]
Message-ID: <846feea6-e2b6-3a0e-b05f-d70e898f9ea5@gmail.com> (raw)
In-Reply-To: <CA+Px+wU1S1EqtW-yZH9z9aCF3ggSriBqy73SRYy8q61x0GkdQQ@mail.gmail.com>
On 17/07/2020 05:27, Tzung-Bi Shih wrote:
> I am not convinced the pop comes from 128f825aeab7.
Maybe some pre-existing defect in rk3399_gru_sound got exposed by
128f825aeab7 or the machine driver needs some changes to complement
that commit?
> (I don't have a rk3399-gru-kevin so I got another test machine with MAX98357A.)
> (I was testing with and without an audio server.)
Your observations are also a bit different from mine, which IMO also
suggests the machine driver is the true culprit -- I'd guess the pops
you hear would be from a different problem in your test machine's
machine driver?
(Let me restate my observations to contrast with yours, as I feel my
previous explanation was too wordy:)
> Observations:
> - I can hear the pop either with or without 128f825aeab7 (with and
> without sdmode-delay).
I never hear pops without 128f825aeab7, but always hear pops with it.
(no change when I remove "sdmode-delay" from the device-tree)
> - The pop noise is not always. Higher probability after stopping
> playback than before starting.
I always hear one pop when starting playback, and two pops (with a few
seconds between them) when stopping playback.
next prev parent reply other threads:[~2020-07-20 22:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-16 11:49 Speaker pops with max98357a on rk3399-gru-kevin since v5.7 Alper Nebi Yasak
2020-07-17 2:27 ` Tzung-Bi Shih
2020-07-20 22:40 ` Alper Nebi Yasak [this message]
2020-07-21 11:46 ` Tzung-Bi Shih
2020-07-21 13:31 ` Alper Nebi Yasak
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=846feea6-e2b6-3a0e-b05f-d70e898f9ea5@gmail.com \
--to=alpernebiyasak@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=heiko@sntech.de \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=tzungbi@google.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