tree 5ece7f5815ea12499dee7a6cc207be11bf9d9e59
parent 673e851b7da81256e73fb738c550ec39bac1c9ff
author Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com> 1622698845 +0300
committer Mark Brown <broonie@kernel.org> 1624277316 +0100
gpgsig -----BEGIN PGP SIGNATURE-----
 
 iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmDQgUQACgkQJNaLcl1U
 h9CVFAf/UeghxIj90FNJyYIzoelFvDneWe2OE6opddJ5jkChXv83XqImOlc1ws8r
 fdNxET+1gaZHVjOV6d84FkpnHnf94nnjJubf0Y4DZBnjpOQml7cf8AMFoSioZj57
 uo7aGXpYyAIfPimKSGvBWqDiBWW7G4WvjUCpmzxpjUy3P3p29eC+V7H8DlxT0zTG
 RCUAmdR6zl5XcJGLFFaAx5f2ct4FzNNZnuRfiJR317bot51h4ZUkZUCSb5cmWnkJ
 vIVyIs1RMQoPDe0T7WaRfFCrlwlmmm8CAtjlHFzL/d1+MqK/0MuN06NjOOmSuJ44
 G7DLRLA5PG2MTKRfxs3GVP2zUYcCtQ==
 =MBHh
 -----END PGP SIGNATURE-----

reboot: Add hardware protection power-off

There can be few cases when we need to shut-down the system in order to
protect the hardware. Currently this is done at least by the thermal core
when temperature raises over certain limit.

Some PMICs can also generate interrupts for example for over-current or
over-voltage, voltage drops, short-circuit, ... etc. On some systems
these are a sign of hardware failure and only thing to do is try to
protect the rest of the hardware by shutting down the system.

Add shut-down logic which can be used by all subsystems instead of
implementing the shutdown in each subsystem. The logic is stolen from
thermal_core with difference of using atomic_t instead of a mutex in
order to allow calls directly from IRQ context and changing the WARN()
to pr_emerg() as discussed here:
https://lore.kernel.org/lkml/YJuPwAZroVZ%2Fw633@alley/
and here:
https://lore.kernel.org/linux-iommu/20210331093104.383705-4-geert+renesas@glider.be/

Signed-off-by: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
Acked-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Link: https://lore.kernel.org/r/e83ec1ca9408f90c857ea9dcdc57b14d9037b03f.1622628333.git.matti.vaittinen@fi.rohmeurope.com
Signed-off-by: Mark Brown <broonie@kernel.org>