According to the documentation the supervisor.erl module implements one_for_all and one_for_one strategies but I can only find restart of the exiting child (one_for_one) implemented in the code and no check for alternative strategies.
The tests also seem to just use one_for_one.
Maybe it is just fine to implement one_for_one strategy for atomvm devices (for now), but then the documentation could be updated.