kernel/git/stable/linux-stable.git/drivers/power/reset, branch linux-4.18.y

power: vexpress: fix corruption in notifier registration

2018-10-03T23:59:04+00:00

[ Upstream commit 09bebb1adb21ecd04adf7ccb3b06f73e3a851e93 ] Vexpress platforms provide two different restart handlers: SYS_REBOOT that restart the entire system, while DB_RESET only restarts the daughter board containing the CPU. DB_RESET is overridden by SYS_REBOOT if it exists. notifier_chain_register used in register_restart_handler by design relies on notifiers to be registered once only, however vexpress restart notifier can get registered twice. When this happen it corrupts list of notifiers, as result some notifiers can be not called on proper event, traverse on list can be cycled forever, and second unregister can access already freed memory. So far, since this was the only restart handler in the system, no issue was observed even if the same notifier was registered twice. However commit 6c5c0d48b686 ("watchdog: sp805: add restart handler") added support for SP805 restart handlers and since the system under test contains two vexpress restart and two SP805 watchdog instances, it was observed that during the boot traversing the restart handler list looped forever as there's a cycle in that list resulting in boot hang. This patch fixes the issues by ensuring that the notifier is installed only once. Cc: Sebastian Reichel Signed-off-by: Sudeep Holla Fixes: 46c99ac66222 ("power/reset: vexpress: Register with kernel restart handler") Signed-off-by: Sebastian Reichel Signed-off-by: Sasha Levin Signed-off-by: Greg Kroah-Hartman

gpio-poweroff: Use gpiod_set_value_cansleep

2018-04-25T21:05:59+00:00

The power-off call is done in a context that must be able to sleep, so use gpiod_set_value_cansleep instead of the atomic gpiod_set_value call. This fixes a kernel warning at shutdown when the gpio is controlled through an IO expander for example. Signed-off-by: Mike Looijmans Signed-off-by: Sebastian Reichel

power: reset: at91-reset: Switch from the pr_() to the dev_() logging functions

2018-03-19T19:51:17+00:00

Use dev_info() instead of pr_info(). Signed-off-by: Ladislav Michl Acked-by: Nicolas Ferre Signed-off-by: Sebastian Reichel

power: reset: at91-poweroff: Remove redundant dev_err call in at91_poweroff_probe()

2018-03-19T19:50:51+00:00

There is an error message within devm_ioremap_resource already, so remove the dev_err call to avoid redundancy. Signed-off-by: Ladislav Michl Acked-by: Nicolas Ferre Signed-off-by: Sebastian Reichel

power: reset: at91-poweroff: Switch from the pr_() to the dev_() logging functions

2018-03-19T19:50:24+00:00

Use dev_info() instead of pr_info(). Signed-off-by: Ladislav Michl Acked-by: Nicolas Ferre Signed-off-by: Sebastian Reichel

power: reset: make function sc27xx_poweroff_shutdown static

2018-03-13T11:10:04+00:00

The function sc27xx_poweroff_shutdown is local to the source and does not need to be in global scope, so make it static. Cleans up sparse warning: drivers/power/reset/sc27xx-poweroff.c:28:6: warning: symbol 'sc27xx_poweroff_shutdown' was not declared. Should it be static? Signed-off-by: Colin Ian King Signed-off-by: Sebastian Reichel

Merge branch 'fixes' into for-next

2018-03-12T13:35:10+00:00

Merge for-stable fixes branch into for-next development branch. Signed-off-by: Sebastian Reichel

power: reset: gpio-poweroff: Support for timeout from device property

2018-03-09T16:15:03+00:00

Add support for reading a timeout value from device property. Fall back to previous default of 3s if nothing is specified. Signed-off-by: Moritz Fischer Signed-off-by: Sebastian Reichel

power: reset: Add Spreadtrum SC27xx PMIC power off support

2018-03-09T16:11:31+00:00

On Spreadtrum platform, we need power off system through external SC27xx series PMICs including the SC2720, SC2721, SC2723, SC2730 and SC2731 chips. Thus this patch adds SC27xx series PMICs power-off support. Signed-off-by: Baolin Wang Signed-off-by: Sebastian Reichel

power: gemini-poweroff: Avoid spurious poweroff

2018-02-22T20:35:04+00:00

On the D-Link DIR-685 we get spurious poweroff from infrared. Since that block (CIR) doesn't even have a driver this can be safely ignored, we can revisit this code once we have a device supporting CIR. On the D-Link DNS-313 we get spurious poweroff from the power button. This appears to be an initialization issue: we need to enable the block (start the state machine) before we clear any dangling IRQ. This patch fixes both issues. Fixes: f7a388d6cd1c ("power: reset: Add a driver for the Gemini poweroff") Signed-off-by: Linus Walleij Signed-off-by: Sebastian Reichel