Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Joao Pinto <Joao.Pinto@synopsys.com>
To: <linux-pci@vger.kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>
Subject: Help request
Date: Wed, 18 Jan 2017 20:46:33 +0000	[thread overview]
Message-ID: <6c47f48a-ec0e-e0ff-bfd6-ae7adf4df828@synopsys.com> (raw)

Hi,

I am testing my 4.80 Root Complex Reference design (PCIe Core 4.80 with iATU
Unroll) and I am facing an issue in kernel v4.9.

My setup is:
ARC Board --- AXI --- HAPS (RC refrence Design) --- Backplane --- USB 3.0 Endpoint

If I use 4.9-rc7 the USB Endpoint gets configured correctly, but when using
4.9-rc8 it does not. I have checked and no changes were made to USB between rc7
and rc8, so there's something in the PCI.

The PCI initialization log seems with more info in 4.9-rc8, so maybe some
operation that causing some confusion in my setup. Could you please give me your
opinion?

Bellow I added the logs for 4.9-rc7 and 4.9-rc8. Thank you for your help!

Joao


***** LOGS for 4.9-rc7:

OF: PCI: host bridge /haps_tunnel/pcie@0xdfc00000 ranges:
OF: PCI:   No bus range found for /haps_tunnel/pcie@0xdfc00000, using [bus 00-ff]
OF: PCI:    IO 0xde000000..0xde00ffff -> 0x00000000
OF: PCI:   MEM 0xd0400000..0xdd3fffff -> 0xd0400000
dw-pcie dfc00000.pcie: link up
dw-pcie dfc00000.pcie: PCI host bridge to bus 0000:00
pci_bus 0000:00: root bus resource [bus 00-ff]
pci_bus 0000:00: root bus resource [io  0x0000-0xffff]
pci_bus 0000:00: root bus resource [mem 0xd0400000-0xdd3fffff]
pci 0000:00:00.0: BAR 8: assigned [mem 0xd0400000-0xd04fffff]
pci 0000:00:00.0: BAR 6: assigned [mem 0xd0500000-0xd050ffff pref]
pci 0000:01:00.0: BAR 0: assigned [mem 0xd0400000-0xd0401fff 64bit]
pci 0000:00:00.0: PCI bridge to [bus 01]
pci 0000:00:00.0:   bridge window [mem 0xd0400000-0xd04fffff]
pci 0000:01:00.0: enabling device (0000 -> 0002)
(...)
xhci_hcd 0000:01:00.0: xHCI Host Controller
xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 3
xhci_hcd 0000:01:00.0: hcc params 0x014042cb hci version 0x96 quirks 0x00000004
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
xhci_hcd 0000:01:00.0: xHCI Host Controller
xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 4

# lspci -v
00:00.0 PCI bridge: Synopsys, Inc. Device eddc (rev 01) (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0, IRQ 45
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
        Memory behind bridge: d0400000-d04fffff
        [virtual] Expansion ROM at d0500000 [disabled] [size=64K]
        Capabilities: [40] Power Management version 3
        Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
        Capabilities: [70] Express Root Port (Slot-), MSI 00
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [148] #19
        Capabilities: [158] Vendor Specific Information: ID=0002 Rev=4 Len=100 <?>
        Kernel driver in use: pcieport

01:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev
03) (prog-if 30 [XHCI])
        Flags: bus master, fast devsel, latency 0, IRQ 46
        Memory at d0400000 (64-bit, non-prefetchable) [size=8K]
        Capabilities: [50] Power Management version 3
        Capabilities: [70] MSI: Enable+ Count=1/8 Maskable- 64bit+
        Capabilities: [90] MSI-X: Enable- Count=8 Masked-
        Capabilities: [a0] Express Endpoint, MSI 00
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [140] Device Serial Number ff-ff-ff-ff-ff-ff-ff-ff
        Capabilities: [150] Latency Tolerance Reporting
        Kernel driver in use: xhci_hcd

****** LOGS for 4.9-rc8:

OF: PCI: host bridge /haps_tunnel/pcie@0xdfc00000 ranges:
OF: PCI:   No bus range found for /haps_tunnel/pcie@0xdfc00000, using [bus 00-ff]
OF: PCI:    IO 0xde000000..0xde00ffff -> 0x00000000
OF: PCI:   MEM 0xd0400000..0xdd3fffff -> 0xd0400000
dw-pcie dfc00000.pcie: link up
dw-pcie dfc00000.pcie: PCI host bridge to bus 0000:00
pci_bus 0000:00: root bus resource [bus 00-ff]
pci_bus 0000:00: root bus resource [io  0x0000-0xffff]
pci_bus 0000:00: root bus resource [mem 0xd0400000-0xdd3fffff]
pci 0000:00:00.0: [16c3:eddc] type 01 class 0x060400
pci 0000:00:00.0: reg 0x38: [mem 0x00000000-0x0000ffff pref]
pci 0000:00:00.0: supports D1
pci 0000:00:00.0: PME# supported from D0 D1 D3hot D3cold
pci 0000:01:00.0: [1033:0194] type 00 class 0x0c0330
pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x00001fff 64bit]
pci 0000:01:00.0: PME# supported from D0 D3hot
pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
pci 0000:00:00.0: BAR 8: assigned [mem 0xd0400000-0xd04fffff]
pci 0000:00:00.0: BAR 6: assigned [mem 0xd0500000-0xd050ffff pref]
pci 0000:01:00.0: BAR 0: assigned [mem 0xd0400000-0xd0401fff 64bit]
pci 0000:00:00.0: PCI bridge to [bus 01]
pci 0000:00:00.0:   bridge window [mem 0xd0400000-0xd04fffff]
aer 0000:00:00.0:pcie002: service driver aer loaded
pci 0000:01:00.0: enabling device (0000 -> 0002)
(...)
xhci_hcd 0000:01:00.0: xHCI Host Controller
xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 3
xhci_hcd 0000:01:00.0: can't setup: -110
xhci_hcd 0000:01:00.0: USB bus 3 deregistered
xhci_hcd 0000:01:00.0: init 0000:01:00.0 fail, -110
xhci_hcd: probe of 0000:01:00.0 failed with error -110

# lspci -v
00:00.0 PCI bridge: Synopsys, Inc. Device eddc (rev 01) (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0, IRQ 45
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
        Memory behind bridge: d0400000-d04fffff
        [virtual] Expansion ROM at d0500000 [disabled] [size=64K]
        Capabilities: [40] Power Management version 3
        Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
        Capabilities: [70] Express Root Port (Slot-), MSI 00
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [148] #19
        Capabilities: [158] Vendor Specific Information: ID=0002 Rev=4 Len=100 <?>
        Kernel driver in use: pcieport

01:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev
03) (prog-if 30 [XHCI])
        Flags: fast devsel
        Memory at d0400000 (64-bit, non-prefetchable) [size=8K]
        Capabilities: [50] Power Management version 3
        Capabilities: [70] MSI: Enable- Count=1/8 Maskable- 64bit+
        Capabilities: [90] MSI-X: Enable- Count=8 Masked-
        Capabilities: [a0] Express Endpoint, MSI 00
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [140] Device Serial Number ff-ff-ff-ff-ff-ff-ff-ff
        Capabilities: [150] Latency Tolerance Reporting



             reply	other threads:[~2017-01-18 20:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-18 20:46 Joao Pinto [this message]
2017-01-20 18:01 ` Help request Joao Pinto
2017-01-20 19:27   ` Bjorn Helgaas
2017-01-23 10:29     ` Joao Pinto

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=6c47f48a-ec0e-e0ff-bfd6-ae7adf4df828@synopsys.com \
    --to=joao.pinto@synopsys.com \
    --cc=bhelgaas@google.com \
    --cc=linux-pci@vger.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