From: Mark Brown <broonie@kernel.org>
To: Sergey Kiselev <sergey.kiselev@intel.com>
Cc: Liam Girdwood <liam.r.girdwood@linux.intel.com>,
Charles Keepax <ckeepax@opensource.wolfsonmicro.com>,
Lars-Peter Clausen <lars@metafoo.de>,
alsa-devel@alsa-project.org, patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH] ASoC: wm8731: initialize the hardware when loading the codec driver
Date: Fri, 5 Jun 2015 19:27:46 +0100 [thread overview]
Message-ID: <20150605182746.GF14071@sirena.org.uk> (raw)
In-Reply-To: <20150605112026.5ec1809046fdd1817691ce05@intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 896 bytes --]
On Fri, Jun 05, 2015 at 11:20:26AM -0700, Sergey Kiselev wrote:
> Charles Keepax <ckeepax@opensource.wolfsonmicro.com> wrote:
> > On Wed, Jun 03, 2015 at 01:19:26PM -0700, Sergey Kiselev wrote:
> > > /* Regulators will have been enabled by bias management */
> > This comment needs an update because this function is only called
> > from the bus probe so no bias management will have been called
> > yet. Basically we are powering down here after probe is complete
> > and the bias management will power us up again.
> I think that's what the comment says (future perfect tense?!). I can
> rephrase it with something simpler like "regulators will be enabled by
> bias management". English is not my mother tongue, and I appreciate any
> corrections. :-)
Yes, will be is better - it binds "will (have been)", that is "it will
at this time be the case that the regulators have been enabled".
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2015-06-05 18:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 20:19 [PATCH] ASoC: wm8731: initialize the hardware when loading the codec driver Sergey Kiselev
2015-06-05 16:25 ` Charles Keepax
2015-06-05 18:20 ` Sergey Kiselev
2015-06-05 18:27 ` Mark Brown [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=20150605182746.GF14071@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=lars@metafoo.de \
--cc=liam.r.girdwood@linux.intel.com \
--cc=patches@opensource.wolfsonmicro.com \
--cc=sergey.kiselev@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