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, 25 Apr 2014 14:14:38 +0000 [thread overview]
Message-ID: <bug-70651-2300-yatEl8Q35H@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-70651-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=70651
Zsolt Barat <zsolt@softmonsters.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |zsolt@softmonsters.com
--- Comment #13 from Zsolt Barat <zsolt@softmonsters.com> ---
Hi,
thanks for your comment on this. I'm running into simmilar issue:
root@lisabook2:~# echo "low">
/sys/class/drm/card0/device/power_dpm_force_performance_level
-bash: echo: write error: Invalid argument
I'm also on a hybrid platform: MBP 8,2 with linux-3.14.0
I recently noticed this, that I can't set this value when I use the machine
*without* an external Monitor which I usually don't.
Does it mean that the kernel now switches automatically to the non dGPU, when
the dGPU is not in use? Would be great news.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-04-25 14:14 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
2014-02-28 14:29 ` bugzilla-daemon
2014-03-01 8:51 ` bugzilla-daemon
2014-04-25 14:14 ` bugzilla-daemon [this message]
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-yatEl8Q35H@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