diff options
author | Simon Glass <sjg@chromium.org> | 2023-06-01 19:23:01 +0300 |
---|---|---|
committer | Tom Rini <trini@konsulko.com> | 2023-07-14 19:54:51 +0300 |
commit | 82cafee133ee5c087449761988c096fc26a17cf6 (patch) | |
tree | 8558fb8f832174e54cc1ed454b163e3b870b36ff /boot/expo.c | |
parent | 7230fdb3837ad745adff4cf129dd04e893fe0a36 (diff) | |
download | u-boot-82cafee133ee5c087449761988c096fc26a17cf6.tar.xz |
expo: Support building an expo from a description file
The only way to create an expo at present is by calling the functions to
create each object. It is useful to have more data-driven approach, where
the objects can be specified in a suitable file format and created from
that. This makes testing easier as well.
Add support for describing an expo in a devicetree node. This allows more
complex tests to be set up, as well as providing an easier format for
users. It also provides a better basis for the upcoming configuration
editor.
Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'boot/expo.c')
-rw-r--r-- | boot/expo.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/boot/expo.c b/boot/expo.c index 8c6fbc0e30..db837f7b49 100644 --- a/boot/expo.c +++ b/boot/expo.c @@ -58,6 +58,7 @@ void expo_destroy(struct expo *exp) uint resolve_id(struct expo *exp, uint id) { + log_debug("resolve id %d\n", id); if (!id) id = exp->next_id++; else if (id >= exp->next_id) |