There are some common pitfalls when using the barebox state framework.
This series has some fixes clarifications to hopefully make usage easier.
First of all it doesn't seem to be clear that the state node in the device
tree the Kernel is started with is created by barebox; a previously existing
node will be replaced. For this reason we now issue a warning when a device
tree contains a state node which does not have any effect.
The userspace barebox-state utility needs a alias which for the state node
(it may work with a full path to the node, like /state, but this has some
additional surprises). We therefore make the alias mandatory so that we
can issue a clear error message when no alias exists and we can make
sure barebox-state will find an alias.
----------------------------------------------------------------
Sascha Hauer (4):
state: Binding: remove @0 from node name
state: warn when a state node will be overwritten
state: Make an alias mandatory
state: Create alias in of_state_fixup()
.../devicetree/bindings/barebox/barebox,state.rst | 8 ++++++-
common/state/state.c | 28 +++++++++++++++++++---
2 files changed, 32 insertions(+), 4 deletions(-)
_______________________________________________
barebox mailing list
barebox@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/barebox
