Messages in this thread | ![/](/images/icornerl.gif) | | Date | Tue, 18 Aug 2020 17:56:18 +0100 | From | Mark Brown <> | Subject | Re: [PATCH] regulator: Avoid grabbing regulator lock during suspend/resume |
| |
On Tue, 4 Aug 2020 00:08:37 -0700, Stephen Boyd wrote: > I see it takes about 5us per regulator to grab the lock, check that this > regulator isn't going to do anything for suspend, and then release the > lock. When that is combined with PMICs that have dozens of regulators we > get into a state where we spend a few miliseconds doing a bunch of > locking operations synchronously to figure out that there's nothing to > do. Let's reorganize the code here a bit so that we don't grab the lock > until we're actually going to do something so that suspend is a little > faster.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[1/1] regulator: Avoid grabbing regulator lock during suspend/resume commit: 0955f5be4337c0ada82e49389249eb99199f8db2
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
| ![\](/images/icornerr.gif) |