summaryrefslogtreecommitdiffstats
path: root/include/linux
diff options
context:
space:
mode:
authorAhmad Fatoum <a.fatoum@pengutronix.de>2020-09-28 16:45:08 +0200
committerSascha Hauer <s.hauer@pengutronix.de>2020-09-29 10:25:02 +0200
commitb28bcba8662cf0e60d35ef30c8d284f320fc9b1c (patch)
tree99e94fa90d1d26a4c7520fd4d3a5a308ec60cff3 /include/linux
parentb42bf25c5bd4baffac1a4f3b40ec0ba10cc13504 (diff)
downloadbarebox-b28bcba8662cf0e60d35ef30c8d284f320fc9b1c.tar.gz
barebox-b28bcba8662cf0e60d35ef30c8d284f320fc9b1c.tar.xz
power: reset: reboot-mode: fix up node into boot device tree
Instead of relying that the kernel and barebox device trees are in sync, just enforce it by having barebox fix up the device tree node it probed into the kernel device tree. We usually want that, but some reboot mode drivers might want to inhibit the fixup, e.g. because they implement a non-upstream binding or because they communicate with the BootROM, while the kernel shouldn't. For those the fixup is made optional via a struct reboot_mode_driver::no_fixup member. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Diffstat (limited to 'include/linux')
-rw-r--r--include/linux/reboot-mode.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/include/linux/reboot-mode.h b/include/linux/reboot-mode.h
index 92a1da7b55..bc57f1d72d 100644
--- a/include/linux/reboot-mode.h
+++ b/include/linux/reboot-mode.h
@@ -11,6 +11,7 @@ struct reboot_mode_driver {
struct device_d *dev;
int (*write)(struct reboot_mode_driver *reboot, u32 magic);
int priority;
+ bool no_fixup;
/* filled by reboot_mode_register */
int reboot_mode_prev, reboot_mode_next;