diff options
| author | Ville Syrjälä <ville.syrjala@linux.intel.com> | 2016-03-07 17:56:57 +0200 |
|---|---|---|
| committer | Ville Syrjälä <ville.syrjala@linux.intel.com> | 2016-03-09 17:06:50 +0200 |
| commit | 8b1f165a4a8f64c28cf42d10e1f4d3b451dedc51 (patch) | |
| tree | 9df06b7376f9bb40bd35e5b684cd65f285fc5b35 /tools/perf/scripts/python/bin/syscall-counts-record | |
| parent | a3c988ea068c94f39a2e6bd37e0faf1c2606a55d (diff) | |
| download | linux-8b1f165a4a8f64c28cf42d10e1f4d3b451dedc51.tar.gz linux-8b1f165a4a8f64c28cf42d10e1f4d3b451dedc51.zip | |
drm/i915: Actually retry with bit-banging after GMBUS timeout
After the GMBUS transfer times out, we set force_bit=1 and
return -EAGAIN expecting the i2c core to call the .master_xfer
hook again so that we will retry the same transfer via bit-banging.
This is in case the gmbus hardware is somehow faulty.
Unfortunately we left adapter->retries to 0, meaning the i2c core
didn't actually do the retry. Let's tell the core we want one retry
when we return -EAGAIN.
Note that i2c-algo-bit also uses this retry count for some internal
retries, so we'll end up increasing those a bit as well.
Cc: Jani Nikula <jani.nikula@intel.com>
Cc: drm-intel-fixes@lists.freedesktop.org
Fixes: bffce907d640 ("drm/i915: abstract i2c bit banging fallback in gmbus xfer")
Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Link: http://patchwork.freedesktop.org/patch/msgid/1457366220-29409-2-git-send-email-ville.syrjala@linux.intel.com
Reviewed-by: Jani Nikula <jani.nikula@intel.com>
Diffstat (limited to 'tools/perf/scripts/python/bin/syscall-counts-record')
0 files changed, 0 insertions, 0 deletions