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: (subset) [PATCH 0/2] regulator: Fix boot speed regression w/ off-on-delay-us
Date: Tue, 14 Mar 2023 16:25:17 +0000 [thread overview]
Message-ID: <167881111741.52189.2713635636188395950.b4-ty@kernel.org> (raw)
In-Reply-To: <20230313181820.2482385-1-dianders@chromium.org>
On Mon, 13 Mar 2023 11:18:18 -0700, Douglas Anderson wrote:
> These two patches together fix a boot speed regression on
> sc7180-trogdor boards which use off-on-delay-us together with
> regulator-boot-on with the eDP power rail.
>
> The first patch is _almost_ a revert of another patch. Depending on
> when the regulator is probed and the actual delay, the end result
> might be the same as a revert or might result in a delay that's
> somewhere between "no delay" and a full delay. As talked about in the
> patch, I believe this is the correct behavior and, if the problems
> fixed in the original patch are still present, I'm hoping that they
> can be fixed in a cleaner way.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[1/2] regulator: core: Shorten off-on-delay-us for always-on/boot-on by time since booted
commit: 691c1fcda5351ed98a44610b7dccc0e3ee920020
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
prev parent reply other threads:[~2023-03-14 16:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 18:18 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
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 ` 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=167881111741.52189.2713635636188395950.b4-ty@kernel.org \
--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®