Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   "Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>
To:     Bjorn Helgaas <helgaas@kernel.org>
CC:     "bjorn@helgaas.com" <bjorn@helgaas.com>,
        "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
        "Mertarg10@gmail.com" <Mertarg10@gmail.com>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        Fran RR <fjrr87@outlook.com>
Subject: RE: Fwd: [Bug 201647] New: Intel Wireless card 3165 does not get
 detected but bluetooth works
Thread-Topic: Fwd: [Bug 201647] New: Intel Wireless card 3165 does not get
 detected but bluetooth works
Thread-Index: AQHUh2ApCc7lmNGfg0mZ5cTxRsuvBaVrCVdwgA10uACAAKnQcIAAWQuAgABN2ZD///8HAIAAIouA///gsoCAACJtkA==
Date:   Tue, 11 Dec 2018 18:51:14 +0000
Message-ID: <0BA3FCBA62E2DC44AF3030971E174FB30133756BE7@HASMSX112.ger.corp.intel.com>
References: <bug-201647-193951@https.bugzilla.kernel.org/>
 <CABhMZUXc4FS-f52ZDsErEhbkm_jjEz+kn75YO5Tuvp42Qm+1xw@mail.gmail.com>
 <20181128211959.GB178809@google.com>
 <0BA3FCBA62E2DC44AF3030971E174FB3013373E4A3@HASMSX112.ger.corp.intel.com>
 <20181210222452.GC85090@google.com>
 <0BA3FCBA62E2DC44AF3030971E174FB30133754C00@HASMSX112.ger.corp.intel.com>
 <20181211135121.GB99796@google.com>
 <0BA3FCBA62E2DC44AF3030971E174FB30133756A29@HASMSX112.ger.corp.intel.com>
 <20181211182630.GF99796@google.com>
 <0BA3FCBA62E2DC44AF3030971E174FB30133756B5D@HASMSX112.ger.corp.intel.com>
 <20181211183805.GG99796@google.com>
In-Reply-To: <20181211183805.GG99796@google.com>
Accept-Language: en-US
Content-Language: en-US
dlp-product: dlpe-windows
dlp-version: 11.0.400.15
dlp-reaction: no-action
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 8BIT
MIME-Version: 1.0
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

> 
> On Tue, Dec 11, 2018 at 06:31:47PM +0000, Grumbach, Emmanuel wrote:
> > > On Tue, Dec 11, 2018 at 04:32:25PM +0000, Grumbach, Emmanuel wrote:
> > > > > On Tue, Dec 11, 2018 at 06:35:20AM +0000, Grumbach, Emmanuel
> wrote:
> > > > > > > > > > https://bugzilla.kernel.org/show_bug.cgi?id=201647
> > > > >
> > > > > > FWIW: I saw another problem like this with a 9650 device.
> > > > >
> > > > > Do you have a pointer to any info about this 9650 issue?  Maybe
> > > > > that would have a clue.
> > > >
> > > > I added him here so that you can ask whatever you like :) The
> > > > story is the same. I am attaching a picture I got from the reporter.
> > > > I can confirm that this device ID / subdevice ID is supported by
> > > > the linux
> > > driver.
> > >
> > > Was there a resolution, i.e., if somebody figured out how to make
> > > the
> > > 9650 wifi work, maybe a similar solution would work for the 3165?
> >
> > Unfortunately not, I am stuck there at the exact same point.
> > No Wifi device shows up in lspci...
> 
> Is there a public spec?  My patience for reverse engineering things that are
> documented somewhere that I'm not allowed to see is pretty limited.
> Presumably *you* should be able to see the spec, since this is an Intel device
> and you have an @intel.com address?

Ok, I start to understand. So no, no public spec. I am an Intel employee,
I used to maintain the WiFi driver (iwlwifi). I don't know much about PCI though.
I am definitely not asking you to reverse engineer our device :)
I can try to ask internally what could be going on.
The reason I haven't done so so far and reached out to you is because I am not
aware about switches that we need to toggle to make the device magically
show up. So I thought it'd be related to the PCI core, which take me to the next point...

> 
> From what we can tell so far, I don't *think* this is a PCI issue.  If the device
> doesn't respond to a PCI config access, the PCI core can't really be expected
> to do anything about it.

Ok, thanks. So I understand from you that you didn't see any weird log from the
PCI core saying: "I can see this device, but I can't enumerate it because XYZ".
I tried to look for such a thing but couldn't.

From this point, I guess I can't do much either. I'll try to get info internally.