All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Heiner Kallweit <hkallweit1@gmail.com>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Bjorn Helgaas <bhelgaas@google.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: Lost PCIe PME after a914ff2d78ce ("PCI/ASPM: Don't select CONFIG_PCIEASPM by default")
Date: Fri, 29 May 2020 21:59:00 +0100	[thread overview]
Message-ID: <20200529205900.whx3mxuvt6ijlqwg@srcf.ucam.org> (raw)
In-Reply-To: <20200529202135.GA461617@bjorn-Precision-5520>

On Fri, May 29, 2020 at 03:21:35PM -0500, Bjorn Helgaas wrote:

> Yeah, that makes sense.  I can't remember the details, but I'm pretty
> sure there's a reason why we ask for the whole set of things.  Seems
> like it solved some problem.  I think Matthew Garrett might have been
> involved in that.

This was https://bugzilla.redhat.com/show_bug.cgi?id=638912 - some 
firmware misbehaves unless you pass the same set of supported 
functionality as Windows does.

-- 
Matthew Garrett | mjg59@srcf.ucam.org

  parent reply	other threads:[~2020-05-29 21:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-28 21:44 Lost PCIe PME after a914ff2d78ce ("PCI/ASPM: Don't select CONFIG_PCIEASPM by default") Heiner Kallweit
2020-05-29 18:50 ` Heiner Kallweit
2020-05-29 19:21   ` Bjorn Helgaas
2020-05-29 19:40     ` Heiner Kallweit
2020-05-29 20:09       ` Heiner Kallweit
2020-05-29 20:21         ` Bjorn Helgaas
2020-05-29 20:53           ` Heiner Kallweit
2020-05-29 20:59           ` Matthew Garrett [this message]
2020-05-29 22:26             ` Heiner Kallweit
2020-05-29 22:58               ` Matthew Garrett
2020-05-30  6:33                 ` Heiner Kallweit
2020-05-30  7:14                   ` Matthew Garrett
2020-05-30 11:33                     ` Christoph Hellwig
2020-06-01 10:58                       ` Rafael J. Wysocki
2020-06-01 15:13                       ` Bjorn Helgaas

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=20200529205900.whx3mxuvt6ijlqwg@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=bhelgaas@google.com \
    --cc=helgaas@kernel.org \
    --cc=hkallweit1@gmail.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    /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.