From: James Feeney <james@nurealm.net>
To: "Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>
Cc: dri-devel@lists.freedesktop.org
Subject: atombios_crtc.c - make error messages distinguishable "unable to allocate a PPLL\n"
Date: Mon, 08 Jun 2015 10:26:55 -0600 [thread overview]
Message-ID: <5575C24F.7040406@nurealm.net> (raw)
atombios_crtc.c
In multi-display configurations, especially with three or more displays,
PLL/clock source allocations can fail when there are more crtc's than PLLs.
When attempting to debug these PLL allocation failures in the source code, the
error message displayed in the log, DRM_ERROR("unable to allocate a PPLL\n");,
is not useful because the exact same error message is used for _five_ different
error states/code paths.
These different error states/paths should be distinguished, simply by including
some kind of distinguishing mark with each error message. For instance:
DRM_ERROR("unable to allocate a PPLL ONE\n");
DRM_ERROR("unable to allocate a PPLL TWO\n");
DRM_ERROR("unable to allocate a PPLL THREE\n");
DRM_ERROR("unable to allocate a PPLL FOUR\n");
DRM_ERROR("unable to allocate a PPLL FIVE\n");
Whether the reported error is truly valid because of an actual hardware
limitation, or invalid because of faulty heuristics in the software, is a
separate topic.
Thanks
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2015-06-08 16:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-08 16:26 James Feeney [this message]
2015-06-08 16:30 ` atombios_crtc.c - make error messages distinguishable "unable to allocate a PPLL\n" Christian König
2015-06-08 17:09 ` James Feeney
2015-06-08 17:43 ` Deucher, Alexander
2015-06-08 19:42 ` James Feeney
2015-06-08 20:22 ` Deucher, Alexander
2015-06-10 22:12 ` James Feeney
2015-06-11 9:57 ` Christian König
2015-06-11 13:35 ` Alex Deucher
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=5575C24F.7040406@nurealm.net \
--to=james@nurealm.net \
--cc=alexander.deucher@amd.com \
--cc=christian.koenig@amd.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.