From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 70651] cannot write to power_dpm_force_performance_level: invalid argument (radeon 7730m)
Date: Fri, 28 Feb 2014 09:03:32 +0000 [thread overview]
Message-ID: <bug-70651-2300-ejjgkr7NpP@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-70651-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=70651
--- Comment #10 from Fabio Sangiovanni <sjh+bugzillakernel@sanjioh.org> ---
Hi,
sorry, any news about this?
Is there something I can do to help?
radeon_pm_info still gives clocks and voltages to me, even if the dGPU is
powered off (DynOff in vgaswitcheroo). I don't get 'Chip powered off'.
Am I missing something and everything is ok, or something's wrong with the
patch? I'm willing to make tests on my hardware if it sounds useful, just let
me know.
As stated in my previous comments, I tested 3.14rc4 + patch so far.
I attached the radeon_pm.c source file as it was when I compiled the kernel.
Thanks
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-02-28 9:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-16 0:25 [Bug 70651] New: cannot write to power_dpm_force_performance_level: invalid argument (radeon 7730m) bugzilla-daemon
2014-02-16 10:23 ` [Bug 70651] " bugzilla-daemon
2014-02-21 14:34 ` bugzilla-daemon
2014-02-21 15:15 ` bugzilla-daemon
2014-02-21 15:49 ` bugzilla-daemon
2014-02-23 22:36 ` bugzilla-daemon
2014-02-24 13:29 ` bugzilla-daemon
2014-02-24 15:21 ` bugzilla-daemon
2014-02-24 15:26 ` bugzilla-daemon
2014-02-25 20:24 ` bugzilla-daemon
2014-02-28 9:03 ` bugzilla-daemon [this message]
2014-02-28 14:29 ` bugzilla-daemon
2014-03-01 8:51 ` bugzilla-daemon
2014-04-25 14:14 ` bugzilla-daemon
2014-09-29 18:34 ` 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-70651-2300-ejjgkr7NpP@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