linux-kernel - Re: [PATCH] regulator: core: Respect off_on

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <161911001187.37672.7744154179151628309.b4-ty@kernel.org>
Date:   Thu, 22 Apr 2021 17:48:47 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Vincent Whitchurch <vincent.whitchurch@...s.com>,
        Liam Girdwood <lgirdwood@...il.com>
Cc:     Mark Brown <broonie@...nel.org>, linux-kernel@...r.kernel.org,
        kernel@...s.com
Subject: Re: [PATCH] regulator: core: Respect off_on_delay at startup

On Thu, 22 Apr 2021 10:30:44 +0200, Vincent Whitchurch wrote:
> We currently do not respect off_on_delay the first time we turn on a
> regulator.  This is problematic since the regulator could have been
> turned off by the bootloader, or it could it have been turned off during
> the probe of the regulator driver (such as when regulator-fixed requests
> the enable GPIO), either of which could potentially have happened less
> than off_on_delay microseconds ago before the first time a client
> requests for the regulator to be turned on.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next

Thanks!

[1/1] regulator: core: Respect off_on_delay at startup
      commit: a5ccccb3ec0b052804d03df90c0d08689be54170

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