All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Kai Heng Feng <kai.heng.feng@canonical.com>
Cc: linux-pci@vger.kernel.org,
	Ethan Hsieh <ethan.hsieh@canonical.com>,
	thunderbolt-software@lists.01.org
Subject: Re: Thunderbolt PCIe card doesn't get enumerated at cold boot
Date: Wed, 31 Jan 2018 10:51:50 +0200	[thread overview]
Message-ID: <20180131085150.GS27654@lahna.fi.intel.com> (raw)
In-Reply-To: <4D112585-48B0-4D6D-9176-A9768FD5AC7A@canonical.com>

On Wed, Jan 31, 2018 at 04:23:21PM +0800, Kai Heng Feng wrote:
> Now sure which string to grep, but looks like hotplug is supported.
> Still attach dmesg to let you confirm it’s working.

This one:

[    0.197025] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]                                                                                                                         
[    0.197222] acpi PNP0A08:00: _OSC: platform does not support [PCIeHotplug PME AER]                                                                                                                                
[    0.197408] acpi PNP0A08:00: _OSC: OS now controls [PCIeCapability]               

So native PCIe hotplug is disabled.

  reply	other threads:[~2018-01-31  8:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-30  8:32 Thunderbolt PCIe card doesn't get enumerated at cold boot Kai Heng Feng
2018-01-30 10:23 ` Mika Westerberg
2018-01-30 10:29   ` Kai Heng Feng
2018-01-30 10:37     ` Mika Westerberg
2018-01-31  7:37       ` Kai Heng Feng
2018-01-31  7:53         ` Mika Westerberg
2018-01-31  8:23           ` Kai Heng Feng
2018-01-31  8:51             ` Mika Westerberg [this message]
2018-01-31  9:26               ` Kai Heng Feng
2018-01-31  9:33                 ` 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=20180131085150.GS27654@lahna.fi.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=ethan.hsieh@canonical.com \
    --cc=kai.heng.feng@canonical.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=thunderbolt-software@lists.01.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 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.