linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Dooks <ben.dooks@codethink.co.uk>
To: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	Daire McNamara <daire.mcnamara@microchip.com>
Subject: Re: [PATCH v17 3/3] PCI: microchip: Add host driver for Microchip PCIe controller
Date: Wed, 28 Oct 2020 17:21:31 +0000	[thread overview]
Message-ID: <587df2af-c59e-371a-230c-9c7a614824bd@codethink.co.uk> (raw)
In-Reply-To: <20201022132223.17789-4-daire.mcnamara@microchip.com>

Hi, I have tried applying these patches to the v5.6.16 yocto kernel
supplied for the Icicle board. I've assumed this is a v5.9 patch set
as they don't apply cleanly to v5.6.16 so rebased up to v5.9

The PCie is failing to initialise on the icicle board. Is there
anything else needing to be done to get it working on this board?

Log excerpt from board boot:

> [    2.435747] microchip-pcie e0000000.pci: host bridge /pci@E0000000 ranges:
> [    2.442580] microchip-pcie e0000000.pci: Parsing ranges property...
> [    2.442611] microchip-pcie e0000000.pci:      MEM 0x00e8000000..0x00efffffff -> 0x00e8000000
> [    2.451177] microchip-pcie e0000000.pci: non-prefetchable memory resource required
> [    2.460943] microchip-pcie e0000000.pci: ECAM at [mem 0xe0000000-0xe7ffffff] : ESC[Bfor [bus 00-7f]
> [    2.469607] microchip-pcie e0000000.pci: PCI host bridge to bus 0000:00
> [    2.476287] pci_bus 0000:00: root bus resource [bus 00-7f]
> [    2.481724] pci_bus 0000:00: root bus resource [mem 0xe8000000-0xefffffff pre: ESC[Bf]
> [    2.489186] pci_bus 0000:00: scanning bus
> [    2.489283] pci 0000:00:00.0: [11aa:1556] type 01 class 0x040000
> [    2.495328] pci 0000:00:00.0: reg 0x10: [mem 0x00000000-0x7fffffff 64bit pref: ESC[B]
> [    2.502610] pci 0000:00:00.0: supports D1 D2
> [    2.506942] pci 0000:00:00.0: PME# supported from D0 D1 D2 D3hot D3cold
> [    2.513544] pci 0000:00:00.0: PME# disabled
> [    2.514859] pci_bus 0000:00: fixups for bus
> [    2.514882] pci 0000:00:00.0: scanning [bus 00-00] behind bridge, pass 0
> [    2.514900] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
> [    2.522847] pci 0000:00:00.0: scanning [bus 00-00] behind bridge, pass 1
> [    2.522972] pci_bus 0000:01: scanning bus
> [    2.573878] pci_bus 0000:01: fixups for bus
> [    2.573897] pci_bus 0000:01: bus scan returning with max=01
> [    2.573918] pci_bus 0000:01: busn_res: [bus 01-7f] end is updated to 01
> [    2.580477] pci_bus 0000:00: bus scan returning with max=01
> [    2.580530] pci 0000:00:00.0: BAR 0: no space for [mem size 0x80000000 64bit pref]
> [    2.588195] pci 0000:00:00.0: BAR 0: failed to assign [mem size 0x80000000 64bit pref]
> [    2.596168] pci 0000:00:00.0: BAR 8: no space for [mem size 0x00200000]
> [    2.602782] pci 0000:00:00.0: BAR 8: failed to assign [mem size 0x00200000]
> [    2.609887] pci 0000:00:00.0: BAR 9: assigned [mem 0xe8000000-0xe81fffff 64bit pref]
> [    2.617692] pci 0000:00:00.0: BAR 7: no space for [io  size 0x1000]
> [    2.624028] pci 0000:00:00.0: BAR 7: failed to assign [io  size 0x1000]
> [    2.630646] pci 0000:00:00.0: PCI bridge to [bus 01]
>     2.635780] pci 0000:00:00.0:   bridge window [mem 0xe8000000-0xe81fffff 64bi: ESC[Bt pref]


-- 
Ben Dooks				http://www.codethink.co.uk/
Senior Engineer				Codethink - Providing Genius

https://www.codethink.co.uk/privacy.html

  reply	other threads:[~2020-10-29  1:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-22 13:22 [PATCH v17 0/3] PCI: microchip: Add host driver for Microchip PCIe controller daire.mcnamara
2020-10-22 13:22 ` [PATCH v17 1/3] PCI: Call platform_set_drvdata earlier in devm_pci_alloc_host_bridge daire.mcnamara
2020-10-22 13:22 ` [PATCH v17 2/3] dt-bindings: PCI: microchip: Add Microchip PolarFire host binding daire.mcnamara
2020-10-23 16:41   ` Rob Herring
2020-10-22 13:22 ` [PATCH v17 3/3] PCI: microchip: Add host driver for Microchip PCIe controller daire.mcnamara
2020-10-28 17:21   ` Ben Dooks [this message]
     [not found]     ` <MN2PR11MB426909C2B84E95AF301C404B96100@MN2PR11MB4269.namprd11.prod.outlook.com>
2020-11-02 11:15       ` Ben Dooks
2020-11-18 16:39         ` Lorenzo Pieralisi
2020-11-18 17:04           ` Ben Dooks
     [not found]             ` <MN2PR11MB42693A7C10C71C327763FA8B96E00@MN2PR11MB4269.namprd11.prod.outlook.com>
2020-11-23 11:46               ` Ben Dooks
2020-11-18 16:44         ` Ben Dooks
2020-11-18 16:35   ` Lorenzo Pieralisi

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=587df2af-c59e-371a-230c-9c7a614824bd@codethink.co.uk \
    --to=ben.dooks@codethink.co.uk \
    --cc=daire.mcnamara@microchip.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;
as well as URLs for NNTP newsgroup(s).