From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 115321] radeon runpm falsely disabled on Clevo P170EM
Date: Sat, 16 Jul 2016 13:59:57 +0000 [thread overview]
Message-ID: <bug-115321-2300-iX64Ihr9bE@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-115321-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=115321
--- Comment #13 from Christoph Haag <haagch.christoph@googlemail.com> ---
This seems like a circular dependency.
if ((rdev->flags & RADEON_IS_PX) && radeon_has_atpx_dgpu_power_cntl())
runtime = true;
vga_switcheroo_register_client(rdev->pdev, &radeon_switcheroo_ops,
runtime);
vga_switcheroo_register_client needs to know if runpm is enabled, but the
kernel only knows whether to enable runpm after vga_switcheroo_register_client
has caused radeon_atpx_init to be executed.
--
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:[~2016-07-16 14:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-27 10:17 [Bug 115321] New: radeon runpm falsely disabled on Clevo P170EM bugzilla-daemon
2016-04-14 3:26 ` [Bug 115321] " bugzilla-daemon
2016-04-14 3:26 ` bugzilla-daemon
2016-04-14 15:27 ` bugzilla-daemon
2016-07-15 13:57 ` bugzilla-daemon
2016-07-15 14:19 ` bugzilla-daemon
2016-07-15 15:21 ` bugzilla-daemon
2016-07-15 15:26 ` bugzilla-daemon
2016-07-15 19:30 ` bugzilla-daemon
2016-07-15 19:42 ` bugzilla-daemon
2016-07-16 13:20 ` bugzilla-daemon
2016-07-16 13:39 ` bugzilla-daemon
2016-07-16 13:55 ` bugzilla-daemon
2016-07-16 13:59 ` bugzilla-daemon [this message]
2016-07-16 14:17 ` bugzilla-daemon
2016-08-24 14:07 ` 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-115321-2300-iX64Ihr9bE@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox