All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107296] WARNING: CPU: 0 PID: 370 at drivers/gpu/drm/amd/amdgpu/../display/dc/calcs/dcn_calcs.c:1355 dcn_bw_update_from_pplib+0x16b/0x280 [amdgpu]
Date: Sat, 13 Jul 2019 18:30:40 +0000	[thread overview]
Message-ID: <bug-107296-502-1S4BvxTZfG@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107296-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1821 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=107296

Paul Menzel <paulepanter@users.sourceforge.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |paulepanter@users.sourcefor
                   |                            |ge.net

--- Comment #16 from Paul Menzel <paulepanter@users.sourceforge.net> ---
Could some AMD developer please comment, on how to fix this? Tables(?)
containing “0 kHz” are apparently shipped by vendors, so what to do?

```
static bool verify_clock_values(struct dm_pp_clock_levels_with_voltage *clks)
{
        int i;

        if (clks->num_levels == 0)
                return false;

        for (i = 0; i < clks->num_levels; i++)
                /* Ensure that the result is sane */
                if (clks->data[i].clocks_in_khz == 0)
                        return false;

        return true;
}
```

Should commit 00893681a0ff4 (drm/amd/display: Reject PPLib clock values if they
are invalid) [1] be reverted? Andrew, Tony, Harry?

> drm/amd/display: Reject PPLib clock values if they are invalid
>
> We should be sticking with the default clock values if the values
> obtained from PPLib are bogus.
>
> Signed-off-by: Andrew Jiang <Andrew.Jiang@amd.com>
> Reviewed-by: Tony Cheng <Tony.Cheng@amd.com>
> Acked-by: Harry Wentland <harry.wentland@amd.com>
> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

PS: AMDGPU’s commit messages are too terse, and should be more elaborate.

[1]:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=00893681a0ff41cacecabc3dafe0987593a3d5c5

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3875 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2019-07-13 18:30 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-19 17:13 [Bug 107296] WARNING: CPU: 0 PID: 370 at drivers/gpu/drm/amd/amdgpu/../display/dc/calcs/dcn_calcs.c:1355 dcn_bw_update_from_pplib+0x16b/0x280 [amdgpu] bugzilla-daemon
2018-07-23 14:29 ` bugzilla-daemon
2018-07-23 15:39 ` bugzilla-daemon
2018-08-08 16:20 ` bugzilla-daemon
2018-10-07  1:14 ` bugzilla-daemon
2018-11-11 15:14 ` bugzilla-daemon
2018-12-16 18:34 ` bugzilla-daemon
2019-01-13 16:52 ` bugzilla-daemon
2019-02-17 12:28 ` bugzilla-daemon
2019-02-22 15:05 ` bugzilla-daemon
2019-03-18 23:03 ` bugzilla-daemon
2019-04-29 20:08 ` bugzilla-daemon
2019-05-25 21:46 ` bugzilla-daemon
2019-05-25 22:02 ` bugzilla-daemon
2019-05-27 11:06 ` bugzilla-daemon
2019-07-03  6:49 ` bugzilla-daemon
2019-07-13 18:30 ` bugzilla-daemon [this message]
2019-08-30 20:49 ` bugzilla-daemon
2019-09-12 10:33 ` bugzilla-daemon
2019-09-25 14:16 ` bugzilla-daemon
2019-09-25 14:18 ` bugzilla-daemon
2019-10-17 12:12 ` bugzilla-daemon
2019-11-01 16:16 ` bugzilla-daemon
2019-11-06 16:14 ` bugzilla-daemon
2019-11-19  8:26 ` bugzilla-daemon
2019-11-20  7:56 ` bugzilla-daemon

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=bug-107296-502-1S4BvxTZfG@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --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.