aboutsummaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorNick Nunley <nicholas.d.nunley@intel.com>2020-07-29 17:19:10 -0700
committerTony Nguyen <anthony.l.nguyen@intel.com>2020-08-01 08:17:40 -0700
commit585cdabdfdb73b4434fcb100f5adf588dd777f2e (patch)
treea872b1ca0cb65114b26b62410fe004af5e8d9706 /tools/perf/scripts/python
parentice: mark PM functions as __maybe_unused (diff)
downloadlinux-dev-585cdabdfdb73b4434fcb100f5adf588dd777f2e.tar.xz
linux-dev-585cdabdfdb73b4434fcb100f5adf588dd777f2e.zip
ice: rename misleading grst_delay variable
The grst_delay variable in ice_check_reset contains the maximum time (in 100 msec units) that the driver will wait for a reset event to transition to the Device Active state. The value is the sum of three separate components: 1) The maximum time it may take for the firmware to process its outstanding command before handling the reset request. 2) The value in RSTCTL.GRSTDEL (the delay firmware inserts between first seeing the driver reset request and the actual hardware assertion). 3) The maximum expected reset processing time in hardware. Referring to this total time as "grst_delay" is misleading and potentially confusing to someone checking the code and cross-referencing the hardware specification. Fix this by renaming the variable to "grst_timeout", which is more descriptive of its actual use. Signed-off-by: Nick Nunley <nicholas.d.nunley@intel.com> Tested-by: Andrew Bowers <andrewx.bowers@intel.com> Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions