public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Adam Goode <adam@spicenitz.org>
Cc: Andreas Noever <andreas.noever@gmail.com>,
	linux-kernel@vger.kernel.org,
	Matthew Garrett <mjg59@srcf.ucam.org>
Subject: Re: Thunderbolt hotplug not working on MacMini7,1
Date: Thu, 23 Apr 2015 09:24:12 +0200	[thread overview]
Message-ID: <20150423072412.GA9969@kroah.com> (raw)
In-Reply-To: <CADN=WdqMSmfwDPZCNVqKgRHKBWbgA=-C2BX6ksMWxA2fFUwJHg@mail.gmail.com>

On Wed, Apr 22, 2015 at 10:56:45PM -0400, Adam Goode wrote:
> On Wed, Apr 22, 2015 at 12:05 AM, Adam Goode <adam@spicenitz.org> wrote:
> > (resending in plain text)
> > (please CC me on replies, I am not on LKML)
> >
> > Hi,
> >
> > I have a new Mac Mini (MacMini7,1). This model supports hotplugging of
> > Thunderbolt on Windows 8 and above. Unfortunately hotplug does not
> > seem to be working for me under Linux. I get the default behavior of
> > devices only working if plugged in during boot.
> >
> > Also, the changes made to support Darwin for _OSI seems to make it
> > impossible to override. This makes it hard to test if the ACPI support
> > for Windows 2012 will just work on Linux. I have not built a kernel
> > yet with Darwin _OSI patched out.
> >
> > Any ideas? I think there are 2 ways forward:
> >
> > 1. Fix the thunderbolt code to work with this new Mac.
> > 2. Limit the Darwin _OSI response to a whitelisted set of Mac
> > machines. It seems like new Macs going forward may work best with the
> > standard Windows 2012 response. I don't know if this method would have
> > advantages over #1. The obvious change might be chained hotplugging
> > support. I don't have a chained device to test.
> >
> 
> I have fixed the issue on my machine. On the Mac Mini, the 0x156c
> device has no subvendor or subdevice. When I added the new id to
> nhi_ids, everything worked without changing anything else in the
> kernel. This is in the _OSI("Darwin").
> 
> Perhaps the driver is overmatching on subvendor/subdevice. Is it
> necessary to do so on some models?

Looks like it.

Can you send a patch showing the change you made to get this to work?

thanks,

greg k-h

  reply	other threads:[~2015-04-23  7:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CADN=WdrsLoertuPi0Tabb6dmdRAj0d200q=5awq-xL9yE8W=hw@mail.gmail.com>
2015-04-22  4:05 ` Fwd: Thunderbolt hotplug not working on MacMini7,1 Adam Goode
2015-04-23  2:56   ` Adam Goode
2015-04-23  7:24     ` Greg KH [this message]
2015-04-23 10:08     ` Andreas Noever
2015-04-23 13:28       ` Adam Goode
2015-04-23 15:10         ` Adam Goode
2015-04-23 16:12           ` Andreas Noever
2015-04-23 17:15             ` Adam Goode
2015-04-24  4:50               ` Adam Goode
2015-04-24 11:46                 ` Andreas Noever
2015-04-24 18:39                   ` Adam Goode
2015-04-25  4:58                     ` Adam Goode
2015-04-26  2:41                       ` Adam Goode
2015-04-26  3:00                         ` Adam Goode
2015-05-04 13:00                           ` Adam Goode
2015-05-06 10:18                             ` Andreas Noever
2015-04-23 18:12       ` Matthew Garrett
2015-04-24 11:41         ` Andreas Noever

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=20150423072412.GA9969@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=adam@spicenitz.org \
    --cc=andreas.noever@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.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