From: Mark Brown <broonie@kernel.org>
To: Douglas Anderson <dianders@chromium.org>
Cc: mka@chromium.org, christian@kohlschutter.com,
Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] regulator: fixed: Set PROBE_PREFER_ASYNCHRONOUS
Date: Mon, 13 Mar 2023 19:05:02 +0000 [thread overview]
Message-ID: <89bf362b-6c63-447a-ad4b-91385bf26dab@sirena.org.uk> (raw)
In-Reply-To: <20230313111806.2.Iee214b2dd184cb19197db8f97fad7e4adca273be@changeid>
[-- Attachment #1: Type: text/plain, Size: 578 bytes --]
On Mon, Mar 13, 2023 at 11:18:20AM -0700, Douglas Anderson wrote:
> As of commit 218320fec294 ("regulator: core: Fix off-on-delay-us for
> always-on/boot-on regulators"), we now might have a big delay during
> probe of fixed regulators. That can have a significant boot speed
> impact. Let's mitigate this by preferring async probe for fixed
> regulators. The regulator framework itself has no issues with
> regulators probing in an asynchronous way. The fixed regulator driver
> is fairly straightforward and also has no issues.
This is going to be true for all regulators...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-03-13 19:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 18:18 [PATCH 0/2] regulator: Fix boot speed regression w/ off-on-delay-us Douglas Anderson
2023-03-13 18:18 ` [PATCH 1/2] regulator: core: Shorten off-on-delay-us for always-on/boot-on by time since booted Douglas Anderson
2023-03-13 18:18 ` [PATCH 2/2] regulator: fixed: Set PROBE_PREFER_ASYNCHRONOUS Douglas Anderson
2023-03-13 19:05 ` Mark Brown [this message]
2023-03-13 19:49 ` Doug Anderson
2023-03-14 13:28 ` Mark Brown
2023-03-14 16:35 ` Doug Anderson
2023-03-14 18:53 ` Mark Brown
2023-03-14 16:25 ` (subset) [PATCH 0/2] regulator: Fix boot speed regression w/ off-on-delay-us 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=89bf362b-6c63-447a-ad4b-91385bf26dab@sirena.org.uk \
--to=broonie@kernel.org \
--cc=christian@kohlschutter.com \
--cc=dianders@chromium.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mka@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
all inboxes | Powered by JetHome®