public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jack Coulter <jscinoz@jscinoz.so>
To: Andreas Noever <andreas.noever@gmail.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	linux-acpi@vger.kernel.org,
	"Rafael J. Wysocki" <rafael@kernel.org>
Subject: Re: Thunderbolt 3 (Skylake / Alpine Ridge) hotplug
Date: Tue, 22 Mar 2016 19:11:14 +1100	[thread overview]
Message-ID: <56F0FE22.6050206@jscinoz.so> (raw)
In-Reply-To: <CAMxnaaU0B_47xZuD+vi0=b1_U7kPr7YVF5-Y0q3GP3ez_eo3CQ@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 926 bytes --]

Hi Andreas,

> That is correct. On your device TB should be handled by the firmware.
>
> Björn suggested that we might not be reacting to acpi notifications
> (or pci hotplug interrupts) properly. To confirm this you could try to
> issue a manual pci rescan via
>
> echo "1" > /sys/bus/pci/rescan
>
> This should make the device appear (if the issue lies with our
> handling of hotplug events).
I tried this but unfortunately no additional devices showed up, nor was
any additional dmesg output generated.

> Otherwise you might want to take a look at the ACPI tables and search
> for code which turn off thunderbolt or something like that. Does
> hotplug work under Windows (without additional drivers)?
I'm unable to comment as to whether it works under Windows - I do not
have Windows installed on this machine nor do I have sufficient
unallocated disk space to install it.


Kind regards,
Jack


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2016-03-22  8:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-26  8:10 Thunderbolt 3 (Skylake / Alpine Ridge) hotplug Jack Coulter
2016-03-15 17:29 ` Bjorn Helgaas
2016-03-16 13:22   ` Lukas Wunner
2016-03-22  8:06     ` Jack Coulter
2016-03-22  8:26   ` Jack Coulter
2016-03-15 18:03 ` Andreas Noever
2016-03-22  8:11   ` Jack Coulter [this message]

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=56F0FE22.6050206@jscinoz.so \
    --to=jscinoz@jscinoz.so \
    --cc=andreas.noever@gmail.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=rafael@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