From: Thierry Reding <thierry.reding@gmail.com>
To: Dave Airlie <airlied@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/dp/mst: dump branch OUI in debugfs
Date: Tue, 14 Jul 2015 10:28:09 +0200 [thread overview]
Message-ID: <20150714082808.GC12465@ulmo.nvidia.com> (raw)
In-Reply-To: <1436837679-14551-1-git-send-email-airlied@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1620 bytes --]
On Tue, Jul 14, 2015 at 11:34:39AM +1000, Dave Airlie wrote:
> From: Dave Airlie <airlied@redhat.com>
>
> It appears some MST docks are worse than other, but the only
> way to know is to see the sw revisions in here, so dump
> the branch OUI so we can look at the sw revision.
>
> Signed-off-by: Dave Airlie <airlied@redhat.com>
> ---
> drivers/gpu/drm/drm_dp_mst_topology.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/gpu/drm/drm_dp_mst_topology.c b/drivers/gpu/drm/drm_dp_mst_topology.c
> index 8a3bfcd..e17a639 100644
> --- a/drivers/gpu/drm/drm_dp_mst_topology.c
> +++ b/drivers/gpu/drm/drm_dp_mst_topology.c
> @@ -2657,6 +2657,11 @@ void drm_dp_mst_dump_topology(struct seq_file *m,
> seq_printf(m, "%02x ", buf[i]);
> seq_printf(m, "\n");
>
> + ret = drm_dp_dpcd_read(mgr->aux, DP_BRANCH_OUI, buf, DP_RECEIVER_CAP_SIZE);
According to the specification, the OUI is 24-bit, whereas the receiver
capability field is 15 bytes (well, at least that is the value defined
for DP_RECEIVER_CAP_SIZE)...
> + seq_printf(m, "branch oui: ");
> + for (i = 0; i < DP_RECEIVER_CAP_SIZE; i++)
> + seq_printf(m, "%02x ", buf[i]);
> + seq_printf(m, "\n");
So this will really dump out more than just the OUI. Perhaps it'd be
worth splitting that up further? 0x503 to 0x508 is an identification
string and displaying it as string would presumably be more useful than
the hexdump equivalent. Similarly 0x509 is a hardware revision and
0x50a/0x50b the firmware major/minor version, which might be more
readable in an idiomatic format (X.Y).
Thierry
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 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:[~2015-07-14 8:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 1:34 [PATCH] drm/dp/mst: dump branch OUI in debugfs Dave Airlie
2015-07-14 8:28 ` Thierry Reding [this message]
2015-07-15 0:09 ` 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=20150714082808.GC12465@ulmo.nvidia.com \
--to=thierry.reding@gmail.com \
--cc=airlied@gmail.com \
--cc=dri-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.