[roll] Roll fuchsia [lowpan][ot-radio] Retry reset if rcp hangs Sometimes RCP does not behave correctly for the soft/hard reset. It does not send the reset event frame and the interrupt back, causing the termination of ot-stack. The failure is propagated through ot-stack, lowpan-spinel-driver, all the way to the client of lowpan service, causing termination or reinitialization of multiple components unintentionally. This is an issue that happens no higher than SPI layer, and there is no clear view for the root cause yet. This change is a workaround to retry hard reset when ot-radio driver detects the rcp is not sending back the reset event frame. Typically RCP has 260 ms delay to come back online and sent the reset event frame after its reset pin is asserted for 100 ms. If RCP does not come back on time (within 700 ms before the reset pin is asserted), ot-radio driver is given enough time to try two more hard resets before ot-stack is unhappy and terminate itself. Tried `lowpanctl leave` for 500 iterations back-to-back, and there is no single failure. Original-Bug: 84054 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/580033 Original-Revision: 514cc69e8d0749e7f771e43925dfda487ff05155 GitOrigin-RevId: 052f181e5a243aa633b2714eee692d8ad52c12ff Change-Id: I936b5197ab11343b9b3e517e047f1a3068172c12
This repository contains Fuchsia's Global Integration manifest files.
All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.
Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.