> > > So, if I apply this series, I do see the PCIe bridge and Ethernet > > > device get enumerated, but I don't see the USB3 controller get > > > enumerated. I believe that is a PCIe device behind the same bridge > > > on the > > same Tegra PCIe port. > > > Shouldn't this device show up? > > I have also reproduced this problem. I see somehow no non- > > prefetchable memory is assigned to any of pcie devices. > > Probably that is the reason for USB3 (pci 0000:04:00.0) not getting > > enumerated since it uses only non-prefetchable memory. > > 1. Bus4(on which usb3 device resides) always return 0xffffffff from it's > config space. which means device is not present? > 2. That's why it is not assigned any resources and hence no usb3 probe > happens. > 3. But same bus does return valid info like vendor/device id etc from it's > config space in downstream kernel and hence usb3 probe does happen. > > Thierry, Stephen, > 4. Any idea why bus4 should return 0xffffffff values in upstream kernel? > Anything missing? > 5. Also, how config space of all pcie devices are mapped? I mean if I change > the config space offset in dts file, then also I find correct vendor/device id > etc for bus0/device0/fun0. > So how this mapping happens that even after changing the config space > offset in PCIe address space, it always finds correct vendor/device id. Any idea on this? -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
