diff options
| author | Ville Syrjälä | 2018-09-28 20:03:59 +0200 |
|---|---|---|
| committer | Ville Syrjälä | 2018-12-10 21:33:20 +0100 |
| commit | c978ae9bde582e82a04c63a4071701691dd8b35c (patch) | |
| tree | 9b938d1f3682a2a38822d69b28bbaffcfde0ed4a /drivers/gpu/drm/drm_modeset_lock.c | |
| parent | drm/ast: Remove set but not used variable 'bo' (diff) | |
| download | kernel-qcow2-linux-c978ae9bde582e82a04c63a4071701691dd8b35c.tar.gz kernel-qcow2-linux-c978ae9bde582e82a04c63a4071701691dd8b35c.tar.xz kernel-qcow2-linux-c978ae9bde582e82a04c63a4071701691dd8b35c.zip | |
drm/dp/mst: Configure no_stop_bit correctly for remote i2c xfers
We aren't supposed to force a stop+start between every i2c msg
when performing multi message transfers. This should eg. cause
the DDC segment address to be reset back to 0 between writing
the segment address and reading the actual EDID extension block.
To quote the E-DDC spec:
"... this standard requires that the segment pointer be
reset to 00h when a NO ACK or a STOP condition is received."
Since we're going to touch this might as well consult the
I2C_M_STOP flag to determine whether we want to force the stop
or not.
Cc: Brian Vincent <brainn@gmail.com>
References: https://bugs.freedesktop.org/show_bug.cgi?id=108081
Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20180928180403.22499-1-ville.syrjala@linux.intel.com
Reviewed-by: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
Diffstat (limited to 'drivers/gpu/drm/drm_modeset_lock.c')
0 files changed, 0 insertions, 0 deletions