All of lore.kernel.org
 help / color / mirror / Atom feed
From: dk-arm-linux@gmx.de (Dieter Kiermaier)
To: linux-arm-kernel@lists.infradead.org
Subject: orion/kirkwood pcie issue still open with 2.6.32-rc6 (marvell stock 2.6.22.18 works!)
Date: Wed, 11 Nov 2009 18:46:52 +0100	[thread overview]
Message-ID: <200911111846.52815.dk-arm-linux@gmx.de> (raw)
In-Reply-To: <20091111171916.GC22741@mail.wantstofly.org>

Am Mittwoch 11 November 2009 18:19:16 schrieb Lennert Buytenhek:
> On Wed, Nov 11, 2009 at 06:11:07PM +0100, Dieter Kiermaier wrote:
> 
> > > > 00:01.0 Class 0604: Device 11ab:2211 (rev 01)
> > > >         Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx-
> > > 
> > > The bridge has been told not to forward MEM transactions to the secondary
> > > side, which explains what you're seeing.
> > 
> > Where can I see that the bridge doesn't want to forward mem transactions?
> > Please could you point me to the entry?
> 
> It's the "Mem" one (surprise! :)).  The minus in "Mem-" indicates that
> the bit is disabled in the Control register.
> 
> The PCIe bridge spec says this about this bit:
> 
> 	Controls the bridge?s response as a target to memory accesses
> 	on the primary interface that address a device that resides
> 	behind the bridge in both the non-prefetchable and prefetchable
> 	memory ranges (see Section 3.1) or targets a memory-mapped
> 	location within the bridge itself (see Section 5.1.2.1).
> 
> 
> > > It's odd that this is happening, as normally pci_enable_bridges()
> > > takes care of enabling I/O and MEM decoding on bridges.
> > > 
> > > What other kernel patches are you using?  And can you put a full boot
> > > log somewhere?
> >
> > I don't use other kernel patches (except changed openrd_base_pci_init()
> > as described in my last post).
> 
> Can you apply this patch and make another boot log?
> 
Bootlog from git u-boot:
http://pastebin.com/d129d38a8

Bootlog from stock u-boot:
http://pastebin.com/d2b91d601

But it looks as the printk's will never reached!

Dieter

> 
> diff --git a/drivers/pci/bus.c b/drivers/pci/bus.c
> index cef28a7..fb06be0 100644
> --- a/drivers/pci/bus.c
> +++ b/drivers/pci/bus.c
> @@ -187,9 +187,14 @@ void pci_enable_bridges(struct pci_bus *bus)
>  	struct pci_dev *dev;
>  	int retval;
>  
> +	printk(KERN_INFO "pci_enable_bridges(%p)\n", bus);
> +
>  	list_for_each_entry(dev, &bus->devices, bus_list) {
> +		printk(KERN_INFO "..considering device %p\n", dev);
>  		if (dev->subordinate) {
> +			printk(KERN_INFO "..has subordinate\n", dev);
>  			if (!pci_is_enabled(dev)) {
> +				printk(KERN_INFO "..enabling\n", dev);
>  				retval = pci_enable_device(dev);
>  				pci_set_master(dev);
>  			}
> diff --git a/drivers/pci/setup-bus.c b/drivers/pci/setup-bus.c
> index b636e24..5ab9028 100644
> --- a/drivers/pci/setup-bus.c
> +++ b/drivers/pci/setup-bus.c
> @@ -599,6 +599,8 @@ pci_assign_unassigned_resources(void)
>  {
>  	struct pci_bus *bus;
>  
> +	printk(KERN_INFO "pci_assign_unassigned_resources()\n");
> +
>  	/* Depth first, calculate sizes and alignments of all
>  	   subordinate buses. */
>  	list_for_each_entry(bus, &pci_root_buses, node) {
> @@ -606,6 +608,7 @@ pci_assign_unassigned_resources(void)
>  	}
>  	/* Depth last, allocate resources and update the hardware. */
>  	list_for_each_entry(bus, &pci_root_buses, node) {
> +		printk(KERN_INFO "..allocating resources for bus %p\n", bus);
>  		pci_bus_assign_resources(bus);
>  		pci_enable_bridges(bus);
>  	}
> 
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
> 

  reply	other threads:[~2009-11-11 17:46 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-09  8:33 orion/kirkwood pcie issue still open with rc6 Dieter Kiermaier
2009-11-09  8:49 ` Simon Kagstrom
2009-11-09  9:06   ` Dieter Kiermaier
2009-11-10 15:26     ` Ronen Shitrit
2009-11-11 14:29     ` orion/kirkwood pcie issue still open with 2.6.32-rc6 (marvell stock 2.6.22.18 works!) Dieter Kiermaier
2009-11-11 15:21       ` Lennert Buytenhek
2009-11-11 16:43         ` Dieter Kiermaier
2009-11-11 16:59           ` Lennert Buytenhek
2009-11-11 17:18             ` Dieter Kiermaier
2009-11-11 16:50         ` Dieter Kiermaier
2009-11-11 16:53           ` Lennert Buytenhek
2009-11-11 17:11             ` Dieter Kiermaier
2009-11-11 17:19               ` Lennert Buytenhek
2009-11-11 17:46                 ` Dieter Kiermaier [this message]
2009-11-12  1:35                 ` [PATCH] ARM: enable PCI bridges after assigning resources (was orion/kirkwood pcie issue still open with 2.6.32-rc6 (marvell stock 2.6.22.18 works!)) Maxime Bizon
2009-11-12  7:23                   ` Dieter Kiermaier
2009-11-12  7:31                     ` Simon Kagstrom
2009-11-12  7:42                       ` Dieter Kiermaier
2009-11-12 19:56                   ` Lennert Buytenhek
2009-11-13 14:35                     ` Maxime Bizon

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=200911111846.52815.dk-arm-linux@gmx.de \
    --to=dk-arm-linux@gmx.de \
    --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.