From: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com> To: "Simon Ser" <contact@emersion.fr>, "Michel Dänzer" <michel@daenzer.net>, "Bas Nieuwenhuizen" <bas@basnieuwenhuizen.nl>, "Marek Olšák" <marek.olsak@amd.com>, "Roman Gilg" <subdiff@gmail.com>, "Nicholas Kazlauskas" <nicholas.kazlauskas@amd.com>, "Harry Wentland" <Harry.Wentland@amd.com>, "Mark Yacoub" <markyacoub@chromium.org>, "Sean Paul" <seanpaul@chromium.org>, "Pekka Paalanen" <ppaalanen@gmail.com> Cc: linux-doc@vger.kernel.org, qingqing.zhuo@amd.com, roman.li@amd.com, amd-gfx@lists.freedesktop.org, aurabindo.pillai@amd.com, nicholas.choi@amd.com, dri-devel@lists.freedesktop.org, "Alex Deucher" <alexander.deucher@amd.com>, bhawanpreet.lakha@amd.com, "Christian König" <christian.koenig@amd.com> Subject: [PATCH 4/6] Documentation/gpu: How to collect DTN log Date: Thu, 25 Nov 2021 10:38:28 -0500 [thread overview] Message-ID: <20211125153830.1352994-5-Rodrigo.Siqueira@amd.com> (raw) In-Reply-To: <20211125153830.1352994-1-Rodrigo.Siqueira@amd.com> Introduce how to collect DTN log from debugfs. Signed-off-by: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com> --- Documentation/gpu/amdgpu-dc/amdgpu-dc-debug.rst | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/Documentation/gpu/amdgpu-dc/amdgpu-dc-debug.rst b/Documentation/gpu/amdgpu-dc/amdgpu-dc-debug.rst index 6dbd21f7f59e..40c55a618918 100644 --- a/Documentation/gpu/amdgpu-dc/amdgpu-dc-debug.rst +++ b/Documentation/gpu/amdgpu-dc/amdgpu-dc-debug.rst @@ -58,3 +58,20 @@ In this case, if you have a pipe split, you will see one small red bar at the bottom of the display covering the entire display width and another bar covering the second pipe. In other words, you will see a bit high bar in the second pipe. + +DTN Debug +========= + +DC (DCN) provides an extensive log that dumps multiple details from our +hardware configuration. Via debugfs, you can capture those status values by +using Display Test Next (DTN) log, which can be captured via debugfs by using:: + + cat /sys/kernel/debug/dri/0/amdgpu_dm_dtn_log + +Since this log is updated accordingly with DCN status, you can also follow the +change in real-time by using something like:: + + sudo watch -d cat /sys/kernel/debug/dri/0/amdgpu_dm_dtn_log + +When reporting a bug related to DC, consider attaching this log before and +after you reproduce the bug. -- 2.25.1
WARNING: multiple messages have this Message-ID (diff)
From: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com> To: "Simon Ser" <contact@emersion.fr>, "Michel Dänzer" <michel@daenzer.net>, "Bas Nieuwenhuizen" <bas@basnieuwenhuizen.nl>, "Marek Olšák" <marek.olsak@amd.com>, "Roman Gilg" <subdiff@gmail.com>, "Nicholas Kazlauskas" <nicholas.kazlauskas@amd.com>, "Harry Wentland" <Harry.Wentland@amd.com>, "Mark Yacoub" <markyacoub@chromium.org>, "Sean Paul" <seanpaul@chromium.org>, "Pekka Paalanen" <ppaalanen@gmail.com> Cc: "Alex Deucher" <alexander.deucher@amd.com>, "Christian König" <christian.koenig@amd.com>, aurabindo.pillai@amd.com, qingqing.zhuo@amd.com, roman.li@amd.com, nicholas.choi@amd.com, bhawanpreet.lakha@amd.com, linux-doc@vger.kernel.org, amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org Subject: [PATCH 4/6] Documentation/gpu: How to collect DTN log Date: Thu, 25 Nov 2021 10:38:28 -0500 [thread overview] Message-ID: <20211125153830.1352994-5-Rodrigo.Siqueira@amd.com> (raw) In-Reply-To: <20211125153830.1352994-1-Rodrigo.Siqueira@amd.com> Introduce how to collect DTN log from debugfs. Signed-off-by: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com> --- Documentation/gpu/amdgpu-dc/amdgpu-dc-debug.rst | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/Documentation/gpu/amdgpu-dc/amdgpu-dc-debug.rst b/Documentation/gpu/amdgpu-dc/amdgpu-dc-debug.rst index 6dbd21f7f59e..40c55a618918 100644 --- a/Documentation/gpu/amdgpu-dc/amdgpu-dc-debug.rst +++ b/Documentation/gpu/amdgpu-dc/amdgpu-dc-debug.rst @@ -58,3 +58,20 @@ In this case, if you have a pipe split, you will see one small red bar at the bottom of the display covering the entire display width and another bar covering the second pipe. In other words, you will see a bit high bar in the second pipe. + +DTN Debug +========= + +DC (DCN) provides an extensive log that dumps multiple details from our +hardware configuration. Via debugfs, you can capture those status values by +using Display Test Next (DTN) log, which can be captured via debugfs by using:: + + cat /sys/kernel/debug/dri/0/amdgpu_dm_dtn_log + +Since this log is updated accordingly with DCN status, you can also follow the +change in real-time by using something like:: + + sudo watch -d cat /sys/kernel/debug/dri/0/amdgpu_dm_dtn_log + +When reporting a bug related to DC, consider attaching this log before and +after you reproduce the bug. -- 2.25.1
next prev parent reply other threads:[~2021-11-25 15:40 UTC|newest] Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-25 15:38 [PATCH 0/6] Expand display core documentation Rodrigo Siqueira 2021-11-25 15:38 ` Rodrigo Siqueira 2021-11-25 15:38 ` [PATCH 1/6] Documentation/gpu: Reorganize DC documentation Rodrigo Siqueira 2021-11-25 15:38 ` Rodrigo Siqueira 2021-11-26 10:35 ` Christian König 2021-11-26 15:40 ` Daniel Vetter 2021-11-26 15:40 ` Daniel Vetter 2021-11-26 15:40 ` Daniel Vetter 2021-11-26 15:42 ` Daniel Vetter 2021-11-26 15:42 ` Daniel Vetter 2021-11-26 15:42 ` Daniel Vetter 2021-11-29 12:06 ` Jani Nikula 2021-11-29 12:06 ` Jani Nikula 2021-11-30 15:46 ` Rodrigo Siqueira Jordao 2021-11-30 15:46 ` Rodrigo Siqueira Jordao 2021-11-30 15:48 ` Harry Wentland 2021-11-30 15:48 ` Harry Wentland 2021-11-30 15:59 ` Rodrigo Siqueira Jordao 2021-11-30 15:59 ` Rodrigo Siqueira Jordao 2021-11-30 16:03 ` Harry Wentland 2021-11-30 16:03 ` Harry Wentland 2021-11-30 20:38 ` Yann Dirson 2021-11-30 20:38 ` Yann Dirson 2021-11-30 20:38 ` Yann Dirson 2021-11-25 15:38 ` [PATCH 2/6] Documentation/gpu: Document amdgpu_dm_visual_confirm debugfs entry Rodrigo Siqueira 2021-11-25 15:38 ` Rodrigo Siqueira 2021-11-25 15:38 ` [PATCH 3/6] Documentation/gpu: Document pipe split visual confirmation Rodrigo Siqueira 2021-11-25 15:38 ` Rodrigo Siqueira 2021-11-25 15:38 ` Rodrigo Siqueira [this message] 2021-11-25 15:38 ` [PATCH 4/6] Documentation/gpu: How to collect DTN log Rodrigo Siqueira 2021-11-25 15:38 ` [PATCH 5/6] Documentation/gpu: Add basic overview of DC pipeline Rodrigo Siqueira 2021-11-25 15:38 ` [PATCH 6/6] Documentation/gpu: Add DC glossary Rodrigo Siqueira 2021-11-25 15:38 ` Rodrigo Siqueira 2021-11-29 20:08 ` Alex Deucher 2021-11-29 20:08 ` Alex Deucher 2021-11-29 20:08 ` Alex Deucher 2021-11-29 20:48 ` ydirson 2021-11-29 20:48 ` ydirson 2021-11-29 20:48 ` ydirson 2021-11-30 10:09 ` Christian König 2021-11-30 10:09 ` Christian König 2021-11-30 10:09 ` Christian König 2021-11-30 14:39 ` Alex Deucher 2021-11-30 14:39 ` Alex Deucher 2021-11-30 14:39 ` Alex Deucher 2021-11-30 15:53 ` Rodrigo Siqueira Jordao 2021-11-30 15:53 ` Rodrigo Siqueira Jordao 2021-11-30 15:53 ` Rodrigo Siqueira Jordao 2021-11-30 19:55 ` Yann Dirson 2021-11-30 19:55 ` Yann Dirson 2021-11-30 19:55 ` Yann Dirson
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=20211125153830.1352994-5-Rodrigo.Siqueira@amd.com \ --to=rodrigo.siqueira@amd.com \ --cc=Harry.Wentland@amd.com \ --cc=alexander.deucher@amd.com \ --cc=amd-gfx@lists.freedesktop.org \ --cc=aurabindo.pillai@amd.com \ --cc=bas@basnieuwenhuizen.nl \ --cc=bhawanpreet.lakha@amd.com \ --cc=christian.koenig@amd.com \ --cc=contact@emersion.fr \ --cc=dri-devel@lists.freedesktop.org \ --cc=linux-doc@vger.kernel.org \ --cc=marek.olsak@amd.com \ --cc=markyacoub@chromium.org \ --cc=michel@daenzer.net \ --cc=nicholas.choi@amd.com \ --cc=nicholas.kazlauskas@amd.com \ --cc=ppaalanen@gmail.com \ --cc=qingqing.zhuo@amd.com \ --cc=roman.li@amd.com \ --cc=seanpaul@chromium.org \ --cc=subdiff@gmail.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: linkBe 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.