From: Nicholas Johnson <nicholas.johnson-opensource@outlook.com.au>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"mika.westerberg@linux.intel.com"
<mika.westerberg@linux.intel.com>,
"corbet@lwn.net" <corbet@lwn.net>,
"benh@kernel.crashing.org" <benh@kernel.crashing.org>,
"logang@deltatee.com" <logang@deltatee.com>,
Nicholas Johnson <nicholas.johnson-opensource@outlook.com.au>
Subject: [PATCH v11 0/4] PCI: Patch series to assist Thunderbolt without any BIOS support
Date: Wed, 13 Nov 2019 13:56:10 +0000 [thread overview]
Message-ID: <PS2P216MB07557ACBAFA091DDCAAC092280760@PS2P216MB0755.KORP216.PROD.OUTLOOK.COM> (raw)
Since last time:
No significant changes. Re-post to get attention and to level out the
patch version numbers (some in the series had been incremented and
others stayed the same).
Change name of patch series. In hindsight, this will not "support"
Thunderbolt with no BIOS. It helps, though - it makes it usable.
Something I have not gotten to work is sleep. Suspending tends to crash
the computer if Thunderbolt devices are attached at the time (without
the BIOS support). I have tried to modify the Thunderbolt driver to hit
up the pcie2tbt mailbox on Titan Ridge, but to no avail. There might be
a PERST_N in GPIO which needs asserting - which is difficult.
Nicholas Johnson (4):
PCI: Consider alignment of hot-added bridges when distributing
available resources
PCI: In extend_bridge_window() change available to new_size
PCI: Change extend_bridge_window() to set resource size directly
PCI: Allow extend_bridge_window() to shrink resource if necessary
drivers/pci/setup-bus.c | 182 +++++++++++++++++++---------------------
1 file changed, 88 insertions(+), 94 deletions(-)
--
2.23.0
reply other threads:[~2019-11-13 13:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=PS2P216MB07557ACBAFA091DDCAAC092280760@PS2P216MB0755.KORP216.PROD.OUTLOOK.COM \
--to=nicholas.johnson-opensource@outlook.com.au \
--cc=benh@kernel.crashing.org \
--cc=bhelgaas@google.com \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=mika.westerberg@linux.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).