From: Matthias Kaehlcke <mka@chromium.org>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
alsa-devel@alsa-project.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Brian Norris <briannorris@chromium.org>,
Dylan Reid <dgreid@chromium.org>, huang lin <hl@rock-chips.com>
Subject: Re: [PATCH v2] ASoC: dmic: Add optional wakeup delay
Date: Fri, 16 Feb 2018 09:09:05 -0800 [thread overview]
Message-ID: <20180216170905.GD99727@google.com> (raw)
In-Reply-To: <20180216112801.GA5886@sirena.org.uk>
El Fri, Feb 16, 2018 at 11:28:01AM +0000 Mark Brown ha dit:
> On Thu, Feb 15, 2018 at 06:24:16PM -0800, Matthias Kaehlcke wrote:
> > On some systems a delay is needed after switching on the clocks, to allow
> > the output to stabilize and avoid a popping noise at the beginning of
> > the recording. Add the optional device tree property 'wakeup-delay-ms'
>
> This doesn't apply against current code, please check and resend.
Sorry about that, apparently 6d6c3946d877 ("ASoC: dmic: replace codec
to component") was merged just after syncing my tree. Will rebase and
resend.
prev parent reply other threads:[~2018-02-16 17:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 2:24 [PATCH v2] ASoC: dmic: Add optional wakeup delay Matthias Kaehlcke
2018-02-16 2:24 ` Matthias Kaehlcke
[not found] ` <20180216022416.208265-1-mka-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2018-02-16 2:47 ` Brian Norris
2018-02-16 2:47 ` Brian Norris
2018-02-16 16:47 ` Matthias Kaehlcke
2018-02-16 11:28 ` Mark Brown
2018-02-16 11:28 ` Mark Brown
2018-02-16 17:09 ` Matthias Kaehlcke [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=20180216170905.GD99727@google.com \
--to=mka@chromium.org \
--cc=alsa-devel@alsa-project.org \
--cc=briannorris@chromium.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dgreid@chromium.org \
--cc=hl@rock-chips.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@ti.com \
--cc=robh+dt@kernel.org \
--cc=tiwai@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.