From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 73047] radeon_pm_info should be in sysfs instead of debugfs Date: Sun, 05 Jan 2014 15:21:22 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0699051742==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id F05E1FCBF4 for ; Sun, 5 Jan 2014 07:21:21 -0800 (PST) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces@lists.freedesktop.org Errors-To: dri-devel-bounces@lists.freedesktop.org To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0699051742== Content-Type: multipart/alternative; boundary="1388935281.fC1dE8Fd0.6846"; charset="us-ascii" --1388935281.fC1dE8Fd0.6846 Date: Sun, 5 Jan 2014 15:21:21 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable https://bugs.freedesktop.org/show_bug.cgi?id=3D73047 --- Comment #6 from Christian K=C3=B6nig --- (In reply to comment #5) > Are the minutes of those discussions available somewhere? I'm curious abo= ut > the arguments. radeon_pm_info is not the real hardware state, but rather the state the ker= nel driver thinks the hardware is in. So it's actually not very useful to an end user, except if you want to debug the different states the kernel driver can be into (UVD/performance/battery etc...) I agree that we need a proper sysfs interface to make certain PM functions = and informations available to userspace, but it's definitely not what's inside radeon_pm_info. --=20 You are receiving this mail because: You are the assignee for the bug. --1388935281.fC1dE8Fd0.6846 Date: Sun, 5 Jan 2014 15:21:21 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Comment= # 6 on bug 73047<= /a> from Christian K=C3=B6nig 
(In reply to comment #5=
)
> Are the minutes of those discussions available s=
omewhere? I'm curious about
> the arguments.

radeon_pm_info is not the real hardware state, but rather the state the ker=
nel
driver thinks the hardware is in.

So it's actually not very useful to an end user, except if you want to debug
the different states the kernel driver can be into (UVD/performance/battery
etc...)

I agree that we need a proper sysfs interface to make certain PM functions =
and
informations available to userspace, but it's definitely not what's inside
radeon_pm_info.

You are receiving this mail because: =20=20=20=20=20=20
  • You are the assignee for the bug.
--1388935281.fC1dE8Fd0.6846-- --===============0699051742== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel --===============0699051742==--