<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - i915 i2c-dev failures with recent chips and docking stations"
href="https://bugs.freedesktop.org/show_bug.cgi?id=100954#c18">Comment # 18</a>
on <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - i915 i2c-dev failures with recent chips and docking stations"
href="https://bugs.freedesktop.org/show_bug.cgi?id=100954">bug 100954</a>
from <span class="vcard"><a class="email" href="mailto:rockowitz@minsoft.com" title="Sanford Rockowitz <rockowitz@minsoft.com>"> <span class="fn">Sanford Rockowitz</span></a>
</span></b>
<pre>Here's a vote for getting some variant of the I2C speed change for DDC devices
into the i915 driver, preferably with a module option allowing users to specify
the speed to be used.
Relatedly, it looks like the following change allows for adjusting the DDC/CI
speed for DisplayPort connected monitors, irrespective of video driver. Am I
correct on that?
<a href="https://www.systutorials.com/linux-kernels/600766/drm-dp-add-dp_aux_i2c_speed_khz-module-param-to-set-the-assume-i2c-bus-speed-linux-4-3/">https://www.systutorials.com/linux-kernels/600766/drm-dp-add-dp_aux_i2c_speed_khz-module-param-to-set-the-assume-i2c-bus-speed-linux-4-3/</a>
You're so right about marginal DDC/CI implementations. For my personal rogues'
gallery see: <a href="http://www.ddcutil.com/monitor_notes/">http://www.ddcutil.com/monitor_notes/</a></pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>