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: <174711545303.85774.16753228157201924455.b4-ty@kernel.org>
Date: Tue, 13 May 2025 07:50:53 +0200
From: Mark Brown <broonie@...nel.org>
To: lgirdwood@...il.com, frieder.schrempf@...tron.de, Frank.Li@....com, 
 marex@...x.de, yibin.gong@....com, joy.zou@....com, 
 linux-kernel@...r.kernel.org, 
 Paul Geurts <paul.geurts@...drive-technologies.com>
Cc: martijn.de.gouw@...drive-technologies.com
Subject: Re: [PATCH] regulator: pca9450: Add restart handler

On Mon, 05 May 2025 13:59:36 +0200, Paul Geurts wrote:
> When restarting a CPU powered by the PCA9450 power management IC, it
> is beneficial to use the PCA9450 to power cycle the CPU and all its
> connected peripherals to start up in a known state. The PCA9450 features
> a cold start procedure initiated by an I2C command.
> 
> Add a restart handler so that the PCA9450 is used to restart the CPU.
> The restart handler sends command 0x14 to the SW_RST register,
> initiating a cold reset (Power recycle all regulators except LDO1, LDO2
> and CLK_32K_OUT)
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: pca9450: Add restart handler
      commit: 6157e62b07d9331cc1d4d9d525dab33d45b0e83c

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


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ