From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 201275] Power consumption RX560 idle raised from 7 W to 13 W
Date: Mon, 08 Oct 2018 19:34:55 +0000 [thread overview]
Message-ID: <bug-201275-2300-abENDiPC7g@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-201275-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=201275
--- Comment #25 from quirin.blaeser@freenet.de ---
(In reply to Alex Deucher from comment #24)
> This patch shouldn't have been applied to 4.18. It looks like it was
> autoselected:
> https://lkml.org/lkml/2018/9/15/172
> It should be reverted.
So "[...]the display component was requesting minimum clocks[...]" isn´t an
issue with Polaris?
Is there any QA left?
Avoiding unusual units is a good idea generally, but it should happen very
early in development.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-10-08 19:34 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-28 16:51 [Bug 201275] New: Power consumption RX460 idle raised from 7 W to 13 W bugzilla-daemon
2018-09-28 17:11 ` [Bug 201275] " bugzilla-daemon
2018-09-28 18:14 ` bugzilla-daemon
2018-09-28 21:51 ` bugzilla-daemon
2018-09-29 2:44 ` bugzilla-daemon
2018-09-29 21:20 ` bugzilla-daemon
2018-09-29 21:28 ` bugzilla-daemon
2018-09-30 14:07 ` bugzilla-daemon
2018-10-04 17:56 ` bugzilla-daemon
2018-10-04 17:59 ` [Bug 201275] Power consumption RX560 " bugzilla-daemon
2018-10-04 20:21 ` bugzilla-daemon
2018-10-04 22:48 ` bugzilla-daemon
2018-10-05 2:37 ` bugzilla-daemon
2018-10-05 3:04 ` bugzilla-daemon
2018-10-05 3:41 ` bugzilla-daemon
2018-10-05 3:43 ` bugzilla-daemon
2018-10-05 3:52 ` bugzilla-daemon
2018-10-05 8:25 ` bugzilla-daemon
2018-10-05 11:52 ` bugzilla-daemon
2018-10-05 13:50 ` bugzilla-daemon
2018-10-05 14:44 ` bugzilla-daemon
2018-10-05 22:18 ` bugzilla-daemon
2018-10-06 10:43 ` bugzilla-daemon
2018-10-07 0:34 ` bugzilla-daemon
2018-10-07 9:20 ` bugzilla-daemon
2018-10-08 14:26 ` bugzilla-daemon
2018-10-08 19:34 ` bugzilla-daemon [this message]
2018-10-08 19:42 ` bugzilla-daemon
2018-10-08 19:49 ` bugzilla-daemon
2018-10-08 19:59 ` bugzilla-daemon
2018-10-08 20:58 ` bugzilla-daemon
2018-10-08 20:59 ` bugzilla-daemon
2018-10-09 18:29 ` bugzilla-daemon
2018-10-10 11:39 ` bugzilla-daemon
2018-10-10 13:42 ` bugzilla-daemon
2018-10-18 12:52 ` 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-201275-2300-abENDiPC7g@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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.