platform/chrome: cros_ec_lpc: prepare for hw_protection_shutdown removal

In the general case, a driver doesn't know which of system shutdown or
reboot is the better action to take to protect hardware in an emergency
situation. For this reason, hw_protection_shutdown is going to be removed
in favor of hw_protection_trigger, which defaults to shutdown, but may be
configured at kernel runtime to be a reboot instead.

The ChromeOS EC situation is different as we do know that shutdown is the
correct action as the EC is programmed to force reset after the short
period, thus replace hw_protection_shutdown with __hw_protection_trigger
with HWPROT_ACT_SHUTDOWN as argument to maintain the same behavior.

No functional change.

Link: https://lkml.kernel.org/r/[e-mail]
Signed-off-by: Ahmad Fatoum <[e-mail]>
Acked-by: Tzung-Bi Shih <[e-mail]>
Cc: Benson Leung <[e-mail]>
Cc: Daniel Lezcano <[e-mail]>
Cc: Fabio Estevam <[e-mail]>
Cc: Guenter Roeck <[e-mail]>
Cc: Jonathan Corbet <[e-mail]>
Cc: Liam Girdwood <[e-mail]>
Cc: Lukasz Luba <[e-mail]>
Cc: Mark Brown <[e-mail]>
Cc: Matteo Croce <[e-mail]>
Cc: Matti Vaittinen <[e-mail]>
Cc: "Rafael J. Wysocki" <[e-mail]>
Cc: Rob Herring (Arm) <[e-mail]>
Cc: Rui Zhang <[e-mail]>
Cc: Sascha Hauer <[e-mail]>
Cc: "Serge E. Hallyn" <[e-mail]>
Signed-off-by: Andrew Morton <[e-mail]>

drivers/platform/chrome/cros_ec_lpc.c

···
 		blocking_notifier_call_chain(&ec_dev->panic_notifier, 0, ec_dev);
 		kobject_uevent_env(&ec_dev->dev->kobj, KOBJ_CHANGE, (char **)env);
 		/* Begin orderly shutdown. EC will force reset after a short period. */
-		hw_protection_shutdown("CrOS EC Panic", -1);
+		__hw_protection_trigger("CrOS EC Panic", -1, HWPROT_ACT_SHUTDOWN);
 		/* Do not query for other events after a panic is reported */
 		return;
 	}