linux-kernel - Re: [PATCH 0/4] Support regulator ON/OFF by PMIC state machine.

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 for Android: free password hash cracker in your pocket

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

Date:   Fri, 04 Sep 2020 11:03:42 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Matti Vaittinen <matti.vaittinen@...rohmeurope.com>,
        mazziesaccount@...il.com
Cc:     Liam Girdwood <lgirdwood@...il.com>, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org, Rob Herring <robh+dt@...nel.org>,
        linux-power@...rohmeurope.com
Subject: Re: [PATCH 0/4] Support regulator ON/OFF by PMIC state machine.

On Thu, 3 Sep 2020 21:37:51 +0300, Matti Vaittinen wrote:
> Support regulator enable/disable via BD718(37/47/50) PMIC state machine.
> 
> The ROHM BD718(37/47/50) PMICs are mainly used for powering i.MX8 based
> systems. On some setups the i.MX8 SoC uses a IO line to suspend the
> system. These PMICs support this via PMIC internal HW state machine
> which can be toggled for example by the PMIC_STBY_REQ IO-pin.
> 
> [...]

Applied to

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

Thanks!

[1/4] regulator: bd718x7 initialize regulator config only once
      commit: df9db2541a82ec18c474942a93729420d37fac81
[2/4] regulator: bd71837: add property for omitting ON/OFF control
      commit: 4788c692bec76dc33c646a07a4aaf7e2dd60091e
[3/4] regulator: bd71847: add property for omitting ON/OFF control
      commit: 6656d4462c7ac5ca0bc5d5a8a91a8c98f0fd1409
[4/4] regulator: bd718x7 fix regulator states at SUSPEND
      commit: 1d848d681c4d4e148193b699a6e5f222e8621519

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