zephyr: fix initialization priority to be forward compatible

In upstream Zephyr the initialization of the GPIO module (and most other
drivers) was changed. This breaks our gpio and in return also flash
initialization.

Update both gpio and flash initialization to work with Kconfig and add
a compile time validation to be able to catch this sooner in the future.

BRANCH=none
BUG=none
TEST=zmake testall

Signed-off-by: Yuval Peress <peress@chromium.org>
Change-Id: I44e5867dbf4cb3d5934bf0d0807dcc1aa6c778e1
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2808335
Reviewed-by: Simon Glass <sjg@chromium.org>

1 files changed, 17 insertions, 0 deletions

diff --git a/zephyr/Kconfig.init_priority b/zephyr/Kconfig.init_priority
new file mode 100644
index 0000000000..b8b3ab7195
--- /dev/null
+++ b/zephyr/Kconfig.init_priority
@@ -0,0 +1,17 @@
+# Copyright 2021 The Chromium OS Authors. All rights reserved.
+# Use of this source code is governed by a BSD-style license that can be
+# found in the LICENSE file.
+
+config PLATFORM_EC_FLASH_INIT_PRIORITY
+  int "Init priority of the flash module"
+  default 52
+  help
+    The initialization priority of the flash module. This should always be
+    greater than PLATFORM_EC_GPIO_INIT_PRIORITY.
+
+config PLATFORM_EC_GPIO_INIT_PRIORITY
+  int "Init priority of the GPIO module"
+  default 51
+  help
+    The initialization priority of the GPIO module. This should always happen
+    after the gpio drivers are initialized.