Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759626Ab3E2Pfi (ORCPT ); Wed, 29 May 2013 11:35:38 -0400 Received: from avon.wwwdotorg.org ([70.85.31.133]:42373 "EHLO avon.wwwdotorg.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756387Ab3E2Pfe (ORCPT ); Wed, 29 May 2013 11:35:34 -0400 Message-ID: <51A62042.7070304@wwwdotorg.org> Date: Wed, 29 May 2013 09:35:30 -0600 From: Stephen Warren User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Jay Agarwal CC: "'thierry.reding@avionic-design.de'" , "'linux@arm.linux.org.uk'" , "'bhelgaas@google.com'" , "'olof@lixom.net'" , "'mturquette@linaro.org'" , "'linux-arm-kernel@lists.infradead.org'" , "'linux-tegra@vger.kernel.org'" , "'linux-kernel@vger.kernel.org'" , "'linux-pci@vger.kernel.org'" Subject: Re: [PATCH 4/4] ARM: tegra: pcie: Enable PCIe controller on Cardhu References: <1368010660-31465-1-git-send-email-jagarwal@nvidia.com> <1368010660-31465-4-git-send-email-jagarwal@nvidia.com> <518A8596.7070702@wwwdotorg.org> In-Reply-To: X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2449 Lines: 51 On 05/29/2013 04:10 AM, Jay Agarwal wrote: >>>> 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? I did already reply the same day you sent the original email. My response was: Is there some reset/enable GPIO or regulator that needs to be programmed to enable the PCIe USB3 controller? Take a look at the schematic. If you can make it work by tweaking those GPIOs/... manually, then we can ignore this issue and fix it up later, since it's not directly related to the PCIe controller driver patches. It's more important to get the Ethernet working than USB, I think. To be honest though, I would expect you to be asking around inside NVIDIA to determine the answer here. As the PCIe SW expert, I'd expect you to drive this process. Try asking the Cardhu board and PCIe HW experts within NVIDIA. Did you make any progress on the issues with the Ethernet device? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/