All of lore.kernel.org
 help / color / mirror / Atom feed
From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: NSA310 + DT
Date: Tue, 30 Jul 2013 23:23:16 +0200	[thread overview]
Message-ID: <20130730232316.10dc7019@skate> (raw)
In-Reply-To: <51F814A0.2050403@uni-bremen.de>

Dear Finn Hoffmann,

On Tue, 30 Jul 2013 21:31:44 +0200, Finn Hoffmann wrote:
> # cat /sys/kernel/debug/mvebu-mbus/devices
> [00] 00000000e8010000 - 00000000e8020000 : pcie0.0 (remap 0000000000010000)
> [01] disabled
> [02] disabled
> [03] disabled
> [04] 00000000f4000000 - 00000000f4010000 : nand
> [05] 00000000f5000000 - 00000000f5010000 : sram
> [06] 00000000fff00000 - 0000000100000000 : pcie0.0

Ok, now we have a memory window created, which looks better, but its
addresses are wrong.

> mvebu-pcie pcie-controller.1: PCIe0.0: link up
> mvebu-pcie pcie-controller.1: PCI host bridge to bus 0000:00
> pci_bus 0000:00: root bus resource [io 0x1000-0xfffff]
> pci_bus 0000:00: root bus resource [mem 0xe0000000-0xe7ffffff]
> pci_bus 0000:00: root bus resource [bus 00-ff]
> PCI: bus0: Fast back to back transfers disabled
> pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
> PCI: bus1: Fast back to back transfers disabled
> MVEBU PCI 0.0: new pref mem, base 0xfff0, limit 0xfff0
> MVEBU PCI 0.0: new pref mem, base 0x0, limit 0x0
> mvebu_mbus: cannot add window 'pcie0.0', conflicts with another window
> pci 0000:00:01.0: BAR 9: assigned [mem 0xe0000000-0xe00fffff pref]
> pci 0000:00:01.0: BAR 7: assigned [io 0x10000-0x10fff]
> pci 0000:01:00.0: BAR 6: assigned [mem 0xe0000000-0xe000ffff pref]
> pci 0000:01:00.0: BAR 4: assigned [mem 0xe0010000-0xe0013fff 64bit pref]
> pci 0000:01:00.0: BAR 2: assigned [mem 0xe0014000-0xe0014fff 64bit pref]
> pci 0000:01:00.0: BAR 0: assigned [io 0x10000-0x100ff]
> pci 0000:00:01.0: PCI bridge to [bus 01]
> pci 0000:00:01.0: bridge window [io 0x10000-0x10fff]
> MVEBU PCI 0.0: new io, base 0x1, limit 0x1
> MVEBU PCI 0.0: new mem, base 0xfff0, limit 0x0
> pci 0000:00:01.0: bridge window [mem 0xe0000000-0xe00fffff pref]
> MVEBU PCI 0.0: new pref mem, base 0xe000, limit 0xe000
> mvebu_mbus: cannot add window 'pcie0.0', conflicts with another window

Thanks for this log. I need a bit of time to analyze this with the
PCI-to-PCI bridge specification, and I'll cook up a new patch,
hopefully tomorrow.

Thanks again a lot for taking the time to report this bug and test the
patches,

Thanks!

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  parent reply	other threads:[~2013-07-30 21:23 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <51DC564A.8050002@harsszegi.com>
2013-07-09 19:36 ` NSA310 + DT Andrew Lunn
2013-07-09 20:21   ` Andrew Lunn
2013-07-10  0:53     ` tibor at harsszegi.com
2013-07-10  6:23       ` Andrew Lunn
2013-07-10  8:42         ` tibor at harsszegi.com
2013-07-10 13:41       ` Andrew Lunn
     [not found]         ` <51DD8E8B.2040505@harsszegi.com>
2013-07-10 16:44           ` Tibor Harsszegi
2013-07-10 16:53           ` Andrew Lunn
2013-07-10 16:57             ` Tibor Harsszegi
2013-07-10 17:13               ` Tibor Harsszegi
2013-07-10 17:15                 ` Tibor Harsszegi
2013-07-10 17:23                   ` Andrew Lunn
2013-07-10 17:29                     ` Tibor Harsszegi
2013-07-10  1:01   ` tibor at harsszegi.com
2013-07-10  7:37     ` Andrew Lunn
2013-07-10  8:43       ` tibor at harsszegi.com
     [not found]       ` <51DEDB32.4080101@harsszegi.com>
2013-07-11 16:44         ` gpio_blink_set + Kirkwood Andrew Lunn
2013-07-11 18:32           ` Tibor Harsszegi
2013-07-11 18:37             ` Jason Cooper
2013-07-11 18:52               ` Tibor Harsszegi
2013-07-11 19:44                 ` Jason Cooper
2013-07-29 17:05       ` NSA310 + DT Finn Hoffmann
2013-07-29 19:21         ` Jason Cooper
2013-07-29 20:43           ` Andrew Lunn
     [not found]             ` <51F78DA6.8010307@uni-bremen.de>
     [not found]               ` <20130730144752.GR24782@lunn.ch>
     [not found]                 ` <20130730172407.3aab15c6@skate>
     [not found]                   ` <51F7EBB9.7000504@uni-bremen.de>
     [not found]                     ` <20130730191943.49f8070c@skate>
2013-07-30 18:36                       ` Andrew Lunn
2013-07-30 19:31                         ` Finn Hoffmann
2013-07-30 19:42                           ` Andrew Lunn
2013-07-30 21:23                           ` Thomas Petazzoni [this message]
2013-07-31  9:14                             ` Thomas Petazzoni
2013-07-31  9:43                               ` Finn Hoffmann
2013-07-31  9:51                                 ` Thomas Petazzoni
2013-07-31 11:41                                   ` Finn Hoffmann
2013-07-31 11:47                                     ` Thomas Petazzoni
2013-07-31 16:45                                     ` Andrew Lunn
2013-08-01  8:01                                       ` Finn Hoffmann
2013-08-01 16:04                                         ` Andrew Lunn
2013-08-01 20:43                                           ` Finn Hoffmann
2013-08-02  8:35                                   ` Finn Hoffmann
2013-08-02  8:46                                     ` Thomas Petazzoni

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=20130730232316.10dc7019@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.