Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sanford Rockowitz <rockowitz@minsoft.com>
To: Intel-gfx@lists.freedesktop.org
Subject: i915 I2C failures with recent chips and docking stations
Date: Fri, 5 May 2017 03:53:39 -0400	[thread overview]
Message-ID: <590C2F83.3090103@minsoft.com> (raw)

I am the author of ddcutil (www.ddcutil.com), a Linux utility that
manages monitor settings using DDC/CI. I am seeing a pattern of user
error reports in which I2C communication is not working when a system
with a recent Intel chip, using the i915 driver, is plugged into a
docking station.  Communication works when the video cable is plugged
directly into the laptop.   There also seems to be a correlation with
whether a DisplayPort cable is being used (i.e. the I2C-over-aux path is
being executed), though this correlation is not as clear.

I'm not sure how best to go about reporting these issues.  The usual bug
reporting mechanism asks for detailed information about a specific
system, which I don't have.   What I do have is the ability to see a
pattern.

Because I2C communication is so fragile (dependencies on hardware
quirks, drivers, etc), ddcutil (which is written in C) has an extensive
subsystem devoted to remotely diagnosing user configurations.  It
already reports DDC (i.e. I2C) communication errors, and has interfaces
to udev, libdrm, and x11 libraries.  If there is some i915 specific code
I could add to refine the diagnosis, I would be happy to add that. 
(Note: ddcutil is entirely a user space program, using the i2c-dev
interface.)

Suggestions on how to proceed appreciated.

Sanford Rockowitz

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

             reply	other threads:[~2017-05-05  7:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-05  7:53 Sanford Rockowitz [this message]
2017-05-05  9:59 ` i915 I2C failures with recent chips and docking stations Jani Nikula
2017-05-05 14:05   ` Sanford Rockowitz
2017-05-05 16:49     ` Jani Nikula
2017-05-05 19:47       ` Sanford Rockowitz
2017-05-05 20:09         ` Jani Nikula
2017-05-05 20:27 ` Ville Syrjälä

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=590C2F83.3090103@minsoft.com \
    --to=rockowitz@minsoft.com \
    --cc=Intel-gfx@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox