From: Thierry Reding <thierry.reding@gmail.com>
To: Dave Airlie <airlied@gmail.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 10/10] i915: mst topology dumper in debugfs
Date: Tue, 13 May 2014 10:33:27 +0200 [thread overview]
Message-ID: <20140513083326.GK6754@ulmo> (raw)
In-Reply-To: <1399877207-15868-11-git-send-email-airlied@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 952 bytes --]
On Mon, May 12, 2014 at 04:46:47PM +1000, Dave Airlie wrote:
[...]
> @@ -3813,6 +3838,7 @@ static const struct drm_info_list i915_debugfs_list[] = {
> {"i915_pc8_status", i915_pc8_status, 0},
> {"i915_power_domain_info", i915_power_domain_info, 0},
> {"i915_display_info", i915_display_info, 0},
> + {"i915_dp_mst_info", i915_dp_mst_info, 0},
This isn't really specific to this patch, but I've been thinking for a
while if perhaps it would be a good idea to try to unify debugfs across
drivers to some degree. What I mean by that is try to use common names
for files with similar functionality. Off the top of my head I think a
couple of drivers expose a list of framebuffers via debugfs, mostly
using duplicated code and different file names. Sharing the code would
of course be easy, but I think there may be some advantage to keeping
the names consistent as well.
Given its generic nature, MST sounds like a good candidate as well.
Thierry
[-- Attachment #1.2: Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-05-13 8:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 6:46 [RFC] DisplayPort MST v0.3 Dave Airlie
2014-05-12 6:46 ` [PATCH 01/10] drm/dp_helper: add defines for DP 1.2 and MST support Dave Airlie
2014-05-13 8:51 ` Jingoo Han
2014-05-12 6:46 ` [PATCH 02/10] drm: add DP MST encoder type Dave Airlie
2014-05-12 6:46 ` [PATCH 03/10] drm/i915: add some registers need for displayport MST support Dave Airlie
2014-05-12 6:46 ` [PATCH 04/10] drm/crtc: add interface to reinitialise the legacy mode group Dave Airlie
2014-05-13 8:26 ` Thierry Reding
2014-05-13 10:15 ` Daniel Vetter
2014-05-12 6:46 ` [PATCH 05/10] drm: add a path blob property Dave Airlie
2014-05-13 8:25 ` Thierry Reding
2014-05-12 6:46 ` [PATCH 06/10] drm/helper: add Displayport multi-stream helper (v0.3) Dave Airlie
2014-05-12 6:46 ` [PATCH 07/10] i915: split some DP modesetting code into a separate function Dave Airlie
2014-05-12 6:46 ` [PATCH 08/10] drm/i915: check connector->encoder before using it Dave Airlie
2014-05-12 6:46 ` [PATCH 09/10] i915: add DP 1.2 MST support (v0.3) Dave Airlie
2014-05-13 7:18 ` David Herrmann
2014-05-14 0:03 ` Dave Airlie
2014-05-14 6:05 ` David Herrmann
2014-05-14 8:23 ` Daniel Vetter
2014-05-12 6:46 ` [PATCH 10/10] i915: mst topology dumper in debugfs Dave Airlie
2014-05-13 8:33 ` Thierry Reding [this message]
2014-05-13 10:18 ` Daniel Vetter
2014-05-13 10:40 ` Thierry Reding
2014-05-12 8:25 ` [RFC] DisplayPort MST v0.3 Dave Airlie
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=20140513083326.GK6754@ulmo \
--to=thierry.reding@gmail.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--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