All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phillip Susi <psusi@ubuntu.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	Linux PCI <linux-pci@vger.kernel.org>
Subject: Re: enabling aspm on ati radeon
Date: Fri, 17 May 2013 16:10:07 -0400	[thread overview]
Message-ID: <51968E9F.1010909@ubuntu.com> (raw)
In-Reply-To: <CAErSpo7zESr5_PEyX=1JWEApCuW+yx+j3RKWh=qC-jReRgSXZw@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 5/17/2013 3:52 PM, Bjorn Helgaas wrote:
> I just sent a patch to make lspci decode all possible values
> there. In the PCIe r2.1 spec, only 1 ("L0s") and 3 ("L0s and L1")
> were defined.  The r3 spec added 0 ("not supported") and 2 ("L1"),
> but lspci hadn't quite kept up.

So do you still want the lspci -xxxs output, or was that just to
answer the question of why it said unknown instead of not supported?
Are we then back to no idea?

I notice a number of functions in drivers/pci/pcie/aspm.c that look
like they need used to configure aspm.  The radeon driver does not
appear to call any of them ( grep for aspm came up with nothing ).
Could that be why?  I can't find anything under Documentation/ about
what a driver needs to do to enable aspm.



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJRlo6eAAoJEJrBOlT6nu75lxQIAMwrt4oDHt5MKiRfpPWIkPO4
DLoFtEax1CGy1Gqmhvw8QpzYw+daqWzYw01t2SDd+owLEHVdp8zzqW21TSld83yb
W9EmZH4NLIO9vsR/UqAHhmbbf9ooAwz+O26Vb7EarPtpNxkRHybDSPYVsv7Cs/R7
54gJOefq7SroiiSr31I0dQT8j57SBRjekJJMGsEh+Et2Cxz+z8CwynCYCoNjQdOQ
g89lyifTEdEy2DuXcRfeCcIH1mTNQazjsRu2/P6I+P/klpyS+b9HqMSUUwNUDwc/
eY1SWrbCt9/2XJ/B6ZxYK3Lmy+25m9fUNkQBsp3BqqXkUICHlE8zTm3DMG1rf6g=
=vIor
-----END PGP SIGNATURE-----

  reply	other threads:[~2013-05-17 20:10 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-16  2:25 enabling aspm on ati radeon Phillip Susi
2013-05-16  8:58 ` Rafael J. Wysocki
2013-05-16 16:42   ` Bjorn Helgaas
     [not found]     ` <5195596C.3000406@ubuntu.com>
2013-05-17 17:31       ` Bjorn Helgaas
2013-05-17 18:04         ` Phillip Susi
2013-05-17 19:52           ` Bjorn Helgaas
2013-05-17 20:10             ` Phillip Susi [this message]
2013-05-17 20:24               ` Bjorn Helgaas
2013-05-17 21:12                 ` Phillip Susi
2013-05-17 21:28                   ` Bjorn Helgaas
2013-05-17 23:36                     ` Phillip Susi
2013-05-17 23:52                       ` Bjorn Helgaas
2013-05-18  0:15                         ` Phillip Susi
2013-05-18  0:40                           ` Bjorn Helgaas
2013-05-18  1:20                             ` Phillip Susi
2013-05-20 13:34                               ` Bjorn Helgaas
2013-05-20 20:01                                 ` Rafael J. Wysocki
2013-05-21 13:31                                   ` Phillip Susi
2013-05-21 18:50                                     ` Sebastian
2013-05-24 19:57                                   ` Phillip Susi
2013-05-24 19:57                                     ` Phillip Susi

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=51968E9F.1010909@ubuntu.com \
    --to=psusi@ubuntu.com \
    --cc=bhelgaas@google.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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.