diff options
| author | Viresh Kumar <[email protected]> | 2016-06-22 14:46:41 +0530 |
|---|---|---|
| committer | Greg Kroah-Hartman <[email protected]> | 2016-06-24 16:03:28 -0700 |
| commit | 326f98ac3168cf415f4e1681b3684614bcd79fd3 (patch) | |
| tree | 13dc504be76286b33691821ede0b3ffecee02dce /tools/perf/scripts/python | |
| parent | dbb8cfeba9cc22e091eaec3dfa34ae4c7dc4d241 (diff) | |
greybus: bootrom: Wait for 10 seconds for mode-switch
The greybus SVC core handles events from the SVC serially today. In some
cases the SVC operations may take too long, for example trying to
activate a dummy interface. If another interface receives a mode-switch
mailbox event in that time, the SVC core wouldn't be able to process it
in quickly enough and bootrom driver will print following error:
bootrom 1-3.3.1: Timed out waiting for Interface Mode Switch from the Module
This can be reproduced easily by attaching a 2x2 module along with any
other normal module like camera or speaker, and doing a unipro_reset
from userspace.
The logs suggest this time to be around 6-7 seconds in most of the
cases. Attaching multiple modules with dummy interfaces may make this
worst.
Lets increase the timeout from 5 to 10 seconds for now, also add a FIXME
for the same.
Testing Done: Tested on EVT 2.0 with camera and a 2x2 module.
Signed-off-by: Viresh Kumar <[email protected]>
Tested-by: Bryan O'Donoghue <[email protected]>
Reviewed-by: Johan Hovold <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions