From: Tzung-Bi Shih <tzungbi@google.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: ALSA development <alsa-devel@alsa-project.org>,
Mark Brown <broonie@kernel.org>, Dylan Reid <dgreid@google.com>,
Jimmy Cheng-Yi Chiang <cychiang@google.com>
Subject: Re: [alsa-devel] [PATCH 1/3] ASoC: max98090: remove msleep in PLL unlocked workaround
Date: Thu, 21 Nov 2019 10:37:13 +0800 [thread overview]
Message-ID: <CA+Px+wW6JHfw0KcnBtHC2RdDL4uj=OAsDvxh45Q5O6DbD4Dunw@mail.gmail.com> (raw)
In-Reply-To: <a0ad3c80-c5e7-f875-7c97-e0e0dc36bfc0@linux.intel.com>
On Thu, Nov 21, 2019 at 12:10 AM Pierre-Louis Bossart
<pierre-louis.bossart@linux.intel.com> wrote:
> maybe add a comment here that the off/on sequence is done on purpose (as
> stated in the commit message)?
Will do, thanks.
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2019-11-21 2:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 6:02 [alsa-devel] [PATCH 0/3] ASoC: max98090: fix PLL unlocked workaround-related Tzung-Bi Shih
2019-11-20 6:02 ` [alsa-devel] [PATCH 1/3] ASoC: max98090: remove msleep in PLL unlocked workaround Tzung-Bi Shih
2019-11-20 14:33 ` Pierre-Louis Bossart
2019-11-21 2:37 ` Tzung-Bi Shih [this message]
2019-11-20 6:02 ` [alsa-devel] [PATCH 2/3] ASoC: max98090: exit workaround earlier if PLL is locked Tzung-Bi Shih
2019-11-20 6:02 ` [alsa-devel] [PATCH 3/3] ASoC: max98090: fix possible race conditions Tzung-Bi Shih
2019-11-20 14:32 ` Pierre-Louis Bossart
2019-11-21 2:19 ` Tzung-Bi Shih
2019-11-21 3:20 ` Pierre-Louis Bossart
2019-11-21 6:17 ` Tzung-Bi Shih
2019-11-21 15:08 ` Pierre-Louis Bossart
2019-11-21 16:49 ` Tzung-Bi Shih
2019-11-21 17:20 ` Pierre-Louis Bossart
2019-11-22 7:52 ` Tzung-Bi Shih
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='CA+Px+wW6JHfw0KcnBtHC2RdDL4uj=OAsDvxh45Q5O6DbD4Dunw@mail.gmail.com' \
--to=tzungbi@google.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=cychiang@google.com \
--cc=dgreid@google.com \
--cc=pierre-louis.bossart@linux.intel.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;
as well as URLs for NNTP newsgroup(s).