linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Emmanuel Grumbach <egrumbach@gmail.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Matthew Garrett <matthew.garrett@nebula.com>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Stanislaw Gruszka <sgruszka@redhat.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	John Linville <linville@tuxdriver.com>,
	Roman Yepishev <roman.yepishev@gmail.com>,
	"Guy, Wey-Yi" <wey-yi.w.guy@intel.com>,
	Mike Miller <mike.miller@hp.com>,
	"iss_storagedev@hp.com" <iss_storagedev@hp.com>,
	Guo-Fu Tseng <cooldavid@cooldavid.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Francois Romieu <romieu@fr.zoreil.com>,
	"nic_swsd@realtek.com" <nic_swsd@realtek.com>,
	"aacraid@adaptec.com" <aacraid@adaptec.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: is L1 really disabled in iwlwifi
Date: Fri, 17 May 2013 08:49:01 +0300	[thread overview]
Message-ID: <CANUX_P2YJC+dULEpa0SJ8Ug+ROZ+RVGNg0FS5b_eYD260mAC=Q@mail.gmail.com> (raw)
In-Reply-To: <20130516225535.GA27962@google.com>

>
> I couldn't imagine that silently ignoring the request to disable ASPM
> would be the right thing, but I spent a long time experimenting with
> Windows on qemu, and I think you're right.  Windows 7 also seems to
> ignore the "PciASPMOptOut" directive when we don't have permission
> to manage ASPM.  All the gory details are at
> https://bugzilla.kernel.org/show_bug.cgi?id=57331
>
> The current behavior is definitely confusing.  I hate to rename or change
> pci_disable_link_state() because it's exported and we'd have to maintain
> the old interface for a while anyway.  And I don't really want to return
> failure to drivers, because I think that would encourage people to fiddle
> with the Link Control register directly in the driver, which doesn't seem
> like a good idea.
>
> And you're also right that (as far as I know) there's not an actual
> problem with the current behavior other than the confusion it causes.
>
> So, how about something like the following patch, which just prints a
> warning when we can't do what the driver requested?  I suppose this may
> also be a nuisance, because users will be worried, but they can't actually
> *do* anything about it.  Maybe it should be dev_info() instead.
>

Good for me - now I would be notified that something wrong happened.

      reply	other threads:[~2013-05-17  5:49 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-04  8:41 is L1 really disabled in iwlwifi Emmanuel Grumbach
2013-03-04 13:44 ` 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
     [not found]               ` <CANUX_P2Hy02SnyYS24dyUGLv3wB3L5xkXt8Y1s+8_RG9d5ReAw@mail.gmail.com>
2013-04-02 11:12                 ` Emmanuel Grumbach
2013-04-07 12:23                   ` Emmanuel Grumbach
2013-04-08 16:28                     ` Bjorn Helgaas
     [not found]                       ` <CANUX_P0hpx8NNvX6cJXfOZMNYN8hrEF-gzf9hBN2Uz=k0WiwgA@mail.gmail.com>
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-11 20:26                                     ` Rafael J. Wysocki
2013-05-11 20:22                                       ` Matthew Garrett
2013-05-16 22:55                                         ` Bjorn Helgaas
2013-05-17  5:49                                           ` Emmanuel Grumbach [this message]

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_P2YJC+dULEpa0SJ8Ug+ROZ+RVGNg0FS5b_eYD260mAC=Q@mail.gmail.com' \
    --to=egrumbach@gmail.com \
    --cc=aacraid@adaptec.com \
    --cc=bhelgaas@google.com \
    --cc=cooldavid@cooldavid.org \
    --cc=iss_storagedev@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=matthew.garrett@nebula.com \
    --cc=mike.miller@hp.com \
    --cc=netdev@vger.kernel.org \
    --cc=nic_swsd@realtek.com \
    --cc=rjw@sisk.pl \
    --cc=roman.yepishev@gmail.com \
    --cc=romieu@fr.zoreil.com \
    --cc=sgruszka@redhat.com \
    --cc=wey-yi.w.guy@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).