linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Len Brown <lenb@kernel.org>,
	Mario.Limonciello@dell.com,
	Michael Jamet <michael.jamet@intel.com>,
	Yehezkel Bernat <yehezkel.bernat@intel.com>,
	linux-pci@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [PATCH v3 0/5] PCI: Fixes for native PCIe and ACPI hotplug
Date: Mon, 26 Feb 2018 17:16:07 +0200	[thread overview]
Message-ID: <1519658167.10722.188.camel@linux.intel.com> (raw)
In-Reply-To: <20180226132112.81447-1-mika.westerberg@linux.intel.com>

On Mon, 2018-02-26 at 16:21 +0300, Mika Westerberg wrote:
> Hi,
> 
> When Thunderbolt controller is configured to be in native enumeration
> mode
> it actually includes two slightly different modes. First there is non-
> RTD3
> mode where the Thunderbolt host controller is only present when there
> is a
> device connected. The second one is RTD3 mode where the controller is
> always present.
> 
> In non-RTD3 mode the Thunderbolt host controller (NHI) and USB host
> (xHCI)
> controller are not hotplugged using native PCIe hotplug but instead
> they
> will be hotplugged via BIOS triggered ACPI Notify() to the root port.
> This
> is done to preserve resources since the NHI and xHCI only need 1 MB of
> MMIO
> space and no additional buses. Currently Linux does not support this
> very
> well and ends up failing the hotplug in one way or another. More
> detailed
> explanation is in changelog of patch [4/5].
> 
> This series fixes this issue and in addition includes fixes for few
> other
> issues found during testing on a system that has Thunderbolt
> controller in
> non-RTD3 native PCIe enumeration mode. However, the fixes here are not
> in
> any way Thunderbolt specific and should be applicable to other systems
> as
> well.
> 

FWIW, 
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>

> The previous versions of the patch series can be found here:
> 
>   v2: https://www.spinics.net/lists/linux-pci/msg69186.html
>   v1: https://www.spinics.net/lists/linux-acpi/msg80607.html
> 
> Changes from v2:
> 
>   - Added Rafael's tag to patch [1/5].
>   - Updated changelog of patch [1/5] to include more details about how
> the
>     problem can be observed from dmesg and lspci output.
> 
> Changes from v1:
> 
>   - Drop 'cmax - max ?: 1' and use similar construct than we use in
> second
>     pass loop in patch [1/5].
>   - Drop unnecessary parentheses in patch [1/5].
>   - Added Rafael's tag to patches [2-5/5].
> 
> Mika Westerberg (5):
>   PCI: Make sure all bridges reserve at least one bus number
>   PCI: Take bridge window alignment into account when distributing
> resources
>   PCI: pciehp: Clear Presence Detect and Data Link Layer Status
> Changed on resume
>   ACPI / hotplug / PCI: Do not scan all bridges when native PCIe
> hotplug is used
>   ACPI / hotplug / PCI: Mark stale PCI devices disconnected
> 
>  drivers/pci/hotplug/acpiphp.h      |  1 +
>  drivers/pci/hotplug/acpiphp_glue.c | 78
> ++++++++++++++++++++++++++++++--------
>  drivers/pci/hotplug/pciehp.h       |  2 +-
>  drivers/pci/hotplug/pciehp_core.c  |  2 +-
>  drivers/pci/hotplug/pciehp_hpc.c   | 13 ++++++-
>  drivers/pci/probe.c                | 11 ++++--
>  drivers/pci/setup-bus.c            | 41 +++++++++++++++++++-
>  7 files changed, 126 insertions(+), 22 deletions(-)
> 

-- 
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy

  parent reply	other threads:[~2018-02-26 15:25 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-26 13:21 [PATCH v3 0/5] PCI: Fixes for native PCIe and ACPI hotplug Mika Westerberg
2018-02-26 13:21 ` [PATCH v3 1/5] PCI: Make sure all bridges reserve at least one bus number Mika Westerberg
2018-03-27 18:57   ` Bjorn Helgaas
2018-03-28 11:43     ` Mika Westerberg
2018-03-28 18:09       ` Bjorn Helgaas
2018-03-29 11:59         ` Mika Westerberg
2018-03-31  8:29           ` Lukas Wunner
2018-03-31  8:58             ` Mika Westerberg
2018-03-31  9:12               ` Lukas Wunner
2018-03-31  9:19                 ` Rafael J. Wysocki
2018-03-31  9:20                 ` Mika Westerberg
2018-03-31  9:30                   ` Lukas Wunner
2018-03-31  9:58                     ` Mika Westerberg
2018-03-31 10:18                       ` Lukas Wunner
2018-03-31 10:37                         ` Mika Westerberg
2018-03-31  9:30                   ` Rafael J. Wysocki
2018-03-31  9:56                     ` Mika Westerberg
2018-03-31 10:05                       ` Rafael J. Wysocki
2018-03-31 10:12                         ` Mika Westerberg
2018-02-26 13:21 ` [PATCH v3 2/5] PCI: Take bridge window alignment into account when distributing resources Mika Westerberg
2018-03-27 19:23   ` Bjorn Helgaas
2018-03-28 12:01     ` Mika Westerberg
2018-03-29 21:29       ` Bjorn Helgaas
2018-03-31  9:18         ` Mika Westerberg
2018-02-26 13:21 ` [PATCH v3 3/5] PCI: pciehp: Clear Presence Detect and Data Link Layer Status Changed on resume Mika Westerberg
2018-02-26 13:21 ` [PATCH v3 4/5] ACPI / hotplug / PCI: Do not scan all bridges when native PCIe hotplug is used Mika Westerberg
2018-02-26 13:21 ` [PATCH v3 5/5] ACPI / hotplug / PCI: Mark stale PCI devices disconnected Mika Westerberg
2018-03-27 19:45   ` Bjorn Helgaas
2018-03-27 20:52     ` Lukas Wunner
2018-03-27 22:13       ` Bjorn Helgaas
2018-03-28  6:25         ` Greg Kroah-Hartman
2018-02-26 15:16 ` Andy Shevchenko [this message]
2018-03-15  6:00 ` [PATCH v3 0/5] PCI: Fixes for native PCIe and ACPI hotplug Mika Westerberg
2018-03-26 10:01   ` Mika Westerberg

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=1519658167.10722.188.camel@linux.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=Mario.Limonciello@dell.com \
    --cc=bhelgaas@google.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=michael.jamet@intel.com \
    --cc=mika.westerberg@linux.intel.com \
    --cc=rjw@rjwysocki.net \
    --cc=yehezkel.bernat@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).