Files
linux/drivers/gpu/drm
Wayne Lin c4e4fccc5d drm/dp_mst: correct the shifting in DP_REMOTE_I2C_READ
[Why]
According to DP spec, it should shift left 4 digits for NO_STOP_BIT
in REMOTE_I2C_READ message. Not 5 digits.

In current code, NO_STOP_BIT is always set to zero which means I2C
master is always generating a I2C stop at the end of each I2C write
transaction while handling REMOTE_I2C_READ sideband message. This issue
might have the generated I2C signal not meeting the requirement. Take
random read in I2C for instance, I2C master should generate a repeat
start to start to read data after writing the read address. This issue
will cause the I2C master to generate a stop-start rather than a
re-start which is not expected in I2C random read.

[How]
Correct the shifting value of NO_STOP_BIT for DP_REMOTE_I2C_READ case in
drm_dp_encode_sideband_req().

Changes since v1:(https://patchwork.kernel.org/patch/11312667/)
* Add more descriptions in commit and cc to stable

Fixes: ad7f8a1f9c ("drm/helper: add Displayport multi-stream helper (v0.6)")
Reviewed-by: Harry Wentland <harry.wentland@amd.com>
Signed-off-by: Wayne Lin <Wayne.Lin@amd.com>
Cc: stable@vger.kernel.org
Signed-off-by: Lyude Paul <lyude@redhat.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20200103055001.10287-1-Wayne.Lin@amd.com
2020-01-03 16:56:23 -05:00
..
2019-08-14 18:31:10 +02:00
2019-11-14 05:53:10 +10:00
2019-10-24 17:59:45 +02:00
2019-10-04 17:04:05 +01:00
2019-10-03 16:38:50 +02:00
2019-06-30 09:48:05 +02:00
2019-10-23 12:10:05 +02:00
2019-07-17 12:52:55 +02:00
2019-07-15 18:11:31 +02:00
2019-09-16 15:14:43 +02:00
2019-07-17 12:52:55 +02:00
2019-11-14 05:53:10 +10:00
2019-10-23 11:14:11 -04:00
2019-07-22 21:24:10 +02:00
2019-10-08 18:29:00 +02:00
2019-11-15 08:00:08 +01:00
2019-07-22 21:24:10 +02:00
2019-06-19 12:07:29 +02:00
2019-10-02 16:28:55 +03:00
2019-10-03 16:38:50 +02:00