All of lore.kernel.org
 help / color / mirror / Atom feed
From: Emmanuel Grumbach <egrumbach@gmail.com>
To: linux-pci@vger.kernel.org,
	linux-wireless <linux-wireless@vger.kernel.org>,
	John Linville <linville@tuxdriver.com>
Subject: is L1 really disabled in iwlwifi
Date: Mon, 4 Mar 2013 10:41:14 +0200	[thread overview]
Message-ID: <CANUX_P3F5YhbZX3WGU-j1AGpbXb_T9Bis2ErhvKkFMtDvzatVQ@mail.gmail.com> (raw)

Hi,

In 1a7123cdd9f49cf1c908fb2c16d26f279c88d8c9, John Linville disabled
ASPM for iwlwifi:

	/* W/A - seems to solve weird behavior. We need to remove this if we
	 * don't want to stay in L1 all the time. This wastes a lot of power */
	pci_disable_link_state(pdev, PCIE_LINK_STATE_L0S | PCIE_LINK_STATE_L1 |
			       PCIE_LINK_STATE_CLKPM);

Now, I took a laptop with 3.7.9 (that supports L1) and measured power.
I would expect to see that as long as the driver isn't loaded, the
power consumption is low (L1 enabled), and when I load the driver, the
power consumption rises because L1 gets disabled.
But this is not what I see. I see more the less the same numbers
before and after driver load.
I don't remember exactly the numbers, but I do remember they were low
(around 1mA or so) - but I really need to check.
I also removed the code above, and it didn't change anything.
Can it be that this code doesn't have any effect?

And as you can see, I am not an expert at this...


Emmanuel Grumbach
egrumbach@gmail.com

             reply	other threads:[~2013-03-04  8:41 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-04  8:41 Emmanuel Grumbach [this message]
2013-03-04 13:44 ` is L1 really disabled in iwlwifi John W. Linville
2013-03-04 13:49 ` Stanislaw Gruszka
2013-03-04 14:57   ` Emmanuel Grumbach
2013-03-04 15:11     ` John W. Linville
2013-03-04 15:48     ` Stanislaw Gruszka
2013-03-04 17:58       ` Emmanuel Grumbach
2013-03-17 15:59         ` Roman Yepishev
2013-03-29 18:24         ` Bjorn Helgaas
2013-03-30 18:38           ` Emmanuel Grumbach
2013-03-30 21:26             ` Bjorn Helgaas
2013-04-02 11:10               ` Emmanuel Grumbach
2013-04-02 11:12                 ` Emmanuel Grumbach
2013-04-07 12:23                   ` Emmanuel Grumbach
2013-04-08 16:28                     ` Bjorn Helgaas
2013-04-09  5:29                       ` Emmanuel Grumbach
2013-04-30 10:57                         ` Emmanuel Grumbach
2013-04-30 22:45                           ` Bjorn Helgaas
2013-04-30 22:55                             ` Matthew Garrett
2013-05-01  8:31                               ` Emmanuel Grumbach
2013-05-01 17:13                                 ` Bjorn Helgaas
2013-05-10 22:52                                   ` Bjorn Helgaas
2013-05-10 22:52                                     ` Bjorn Helgaas
2013-05-11 20:26                                     ` Rafael J. Wysocki
2013-05-11 20:26                                       ` Rafael J. Wysocki
2013-05-11 20:22                                       ` Matthew Garrett
2013-05-11 20:22                                         ` Matthew Garrett
2013-05-11 20:22                                         ` Matthew Garrett
2013-05-16 22:55                                         ` Bjorn Helgaas
2013-05-17  5:49                                           ` Emmanuel Grumbach

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=CANUX_P3F5YhbZX3WGU-j1AGpbXb_T9Bis2ErhvKkFMtDvzatVQ@mail.gmail.com \
    --to=egrumbach@gmail.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    /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.