diff options
| author | Ville Syrjälä <ville.syrjala@linux.intel.com> | 2018-09-28 21:03:59 +0300 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2019-04-05 22:34:53 +0200 |
| commit | 36b39631cc851b6b90b22a3aa4a09ee79b0718de (patch) | |
| tree | c3e765fcab409aec3a26c0205087979ed56ad5dd /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | 8826838f43fe879eba8df230e93e2f43ab0b3081 (diff) | |
| download | talos-obmc-linux-36b39631cc851b6b90b22a3aa4a09ee79b0718de.tar.gz talos-obmc-linux-36b39631cc851b6b90b22a3aa4a09ee79b0718de.zip | |
drm/dp/mst: Configure no_stop_bit correctly for remote i2c xfers
[ Upstream commit c978ae9bde582e82a04c63a4071701691dd8b35c ]
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>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions
