public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Durgadoss R <durgadoss.r@intel.com>
Cc: intel-gfx@lists.freedesktop.org, ville.syrjala@intel.com,
	paulo.r.zanoni@intel.com
Subject: Re: [PATCH v3] drm/i915: Add debugfs to read/write any DPCD register
Date: Mon, 20 Apr 2015 09:19:39 -0700	[thread overview]
Message-ID: <20150420161939.GF14565@bremse> (raw)
In-Reply-To: <1429529894-8771-1-git-send-email-durgadoss.r@intel.com>

On Mon, Apr 20, 2015 at 05:08:14PM +0530, Durgadoss R wrote:
> This patch creates a connector specific debugfs
> interface to read any particular DPCD register.
> The DPCD register address (hex format) is written
> to 'i915_dpcd_addr' interface and the corresponding
> value can be read from 'i915_dpcd_val' interface.
> 
> To write into a DPCD register, echo a value into
> 'i915_dpcd_val' interface. This will return -EIO
> for invalid writes.
> 
> Example usage:
> echo 0x2 > i915_dpcd_addr
> cat i915_dpcd_val
> 0x84
> 
> To write 0x1 to DPCD 0x170:
> echo 0x170 > i915_dpcd_addr
> echo 0x1 > i915_dpcd_val
> cat i915_dpcd_val
> 0x1
> 
> v2: Address Jani's comments.
> 
> v3: Added capability to write DPCD also (Ville)
> 
> Signed-off-by: Durgadoss R <durgadoss.r@intel.com>

As mentioned in another thread I think the right approach here is to
expose the dp aux interface through some ioctls in debugfs or dev
somewhere, and then add simple tools on top of that. Similar to what we
have with i2c. That would allow us to implement additional things on top
like mst inspection or using the i2c-over-dp-aux sidechannel.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

      parent reply	other threads:[~2015-04-20 16:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-20 11:38 [PATCH v3] drm/i915: Add debugfs to read/write any DPCD register Durgadoss R
2015-04-20 13:03 ` Sivakumar Thulasimani
2015-04-20 14:36 ` shuang.he
2015-04-20 16:19 ` Daniel Vetter [this message]

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=20150420161939.GF14565@bremse \
    --to=daniel@ffwll.ch \
    --cc=durgadoss.r@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=paulo.r.zanoni@intel.com \
    --cc=ville.syrjala@intel.com \
    /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