linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: "Rafael J . Wysocki" <rafael@kernel.org>,
	"Mika Westerberg" <mika.westerberg@linux.intel.com>,
	"Krzysztof Wilczyński" <kw@linux.com>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Myron Stowe" <myron.stowe@redhat.com>,
	"Juha-Pekka Heikkila" <juhapekka.heikkila@gmail.com>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Ingo Molnar" <mingo@redhat.com>,
	"Borislav Petkov" <bp@alien8.de>,
	"H . Peter Anvin" <hpa@zytor.com>
Cc: "Hans de Goede" <hdegoede@redhat.com>,
	"Benoit Grégoire" <benoitg@coeus.ca>,
	"Hui Wang" <hui.wang@canonical.com>,
	linux-acpi@vger.kernel.org, linux-pci@vger.kernel.org,
	x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v7 0/1] x86/PCI: Ignore E820 reservations for bridge windows on newer systems
Date: Thu,  5 May 2022 17:20:15 +0200	[thread overview]
Message-ID: <20220505152016.5059-1-hdegoede@redhat.com> (raw)

Hi All,

Here is v7 of my patch to address the E820 reservations vs PCI host bridge
ranges issue which are causing touchpad and/or thunderbolt issues on many
different laptop models.

After previous attemps to identify these systems by looking for E820
reservations covering the entire bridge window, which broke the boot
on some coreboot based ChromeBooks we are now back to using a bios date
based approach, now combined with DMI quirks for systems after the
cutoff date which still report a wrong window from their _CRS method
despite them being new(ish).

This is based on top of Bjorn's pci/resource branch:
https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git/log/?h=pci/resource

Regards,

Hans


Hans de Goede (1):
  x86/PCI: Ignore E820 reservations for bridge windows on newer systems

 .../admin-guide/kernel-parameters.txt         |  9 +++
 arch/x86/include/asm/pci_x86.h                |  2 +
 arch/x86/pci/acpi.c                           | 74 ++++++++++++++++++-
 arch/x86/pci/common.c                         |  6 ++
 4 files changed, 89 insertions(+), 2 deletions(-)

-- 
2.36.0


             reply	other threads:[~2022-05-05 15:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-05 15:20 Hans de Goede [this message]
2022-05-05 15:20 ` [PATCH v7 1/1] x86/PCI: Ignore E820 reservations for bridge windows on newer systems Hans de Goede
2022-05-06 16:51   ` Bjorn Helgaas
2022-05-07 10:09     ` Hans de Goede
2022-05-07 15:31       ` Bjorn Helgaas
2022-05-09 17:33         ` Hans de Goede
2022-05-09 18:21           ` Hans de Goede
2022-05-09 19:36           ` Bjorn Helgaas
2022-05-12 19:15             ` Hans de Goede
2022-05-18 22:07           ` Bjorn Helgaas
2022-05-19 14:01             ` Hans de Goede
2022-05-19 14:14               ` Bjorn Helgaas
2022-05-19 14:29                 ` Hans de Goede
2022-05-19 14:49                   ` Bjorn Helgaas
2022-05-19 15:06                     ` Hans de Goede

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=20220505152016.5059-1-hdegoede@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=benoitg@coeus.ca \
    --cc=bhelgaas@google.com \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=hui.wang@canonical.com \
    --cc=juhapekka.heikkila@gmail.com \
    --cc=kw@linux.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=mingo@redhat.com \
    --cc=myron.stowe@redhat.com \
    --cc=rafael@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /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).