From: Lucas Stach <dev@lynxeye.de>
To: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 1/4] pci: fix device registration for directly attached devices
Date: Fri, 10 Apr 2015 09:15:12 +0200 [thread overview]
Message-ID: <1428650112.2182.1.camel@lynxeye.de> (raw)
In-Reply-To: <1428627714-17077-2-git-send-email-sebastian.hesselbarth@gmail.com>
Am Freitag, den 10.04.2015, 03:01 +0200 schrieb Sebastian Hesselbarth:
> Commit b8a1bb1dd215770670108fe5b0de0e5e137bf8fd
> ("pci: defer device registration until after bridge setup")
> removed pci_register_device() from setup_device() to allow
> bridges to be registered before attached sub-devices.
>
> This breaks normal registration for devices that are not
> connected through a bridge. Fix this by calling pci_register_device()
> for normal devices again.
> Signed-off-by: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
NACK: This again breaks devices that are connected through a bridge if
the bridge configuration is invalid at startup.
There is already a patch on the list which should fix this problem "pci:
make sure to activate devices on the root bus".
Could you please test this instead?
> ---
> Cc: barebox@lists.infradead.org
> Cc: Lucas Stach <dev@lynxeye.de>
> ---
> drivers/pci/pci.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
> index d6e95c3ec894..c633d138ca66 100644
> --- a/drivers/pci/pci.c
> +++ b/drivers/pci/pci.c
> @@ -344,6 +344,7 @@ unsigned int pci_scan_bus(struct pci_bus *bus)
> dev->rom_address = (l == 0xffffffff) ? 0 : l;
>
> setup_device(dev, 6);
> + pci_register_device(dev);
> break;
> case PCI_HEADER_TYPE_BRIDGE:
> setup_device(dev, 2);
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2015-04-10 7:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 1:01 [PATCH 0/4] Some fixes for PCI, mvneta, xHCI Sebastian Hesselbarth
2015-04-10 1:01 ` [PATCH 1/4] pci: fix device registration for directly attached devices Sebastian Hesselbarth
2015-04-10 7:15 ` Lucas Stach [this message]
2015-04-10 8:24 ` Sebastian Hesselbarth
2015-04-10 1:01 ` [PATCH 2/4] net: mvneta: Fix transmit errors due to dirty txdesc Sebastian Hesselbarth
2015-04-13 6:43 ` Sascha Hauer
2015-04-10 1:01 ` [PATCH 3/4] net: mvneta: Remove unnecessary DMA ops Sebastian Hesselbarth
2015-04-10 7:23 ` Lucas Stach
2015-04-10 8:18 ` Sebastian Hesselbarth
2015-04-10 16:09 ` Jan Lübbe
2015-04-10 1:01 ` [PATCH 4/4] USB: xHCI: Sync non-coherent DMA buffers Sebastian Hesselbarth
2015-04-10 7:25 ` Lucas Stach
2015-04-13 14:22 ` [PATCH v2] " Sebastian Hesselbarth
2015-04-14 18:52 ` Sascha Hauer
2015-04-14 19:29 ` Sebastian Hesselbarth
2015-04-15 9:11 ` Lucas Stach
2015-04-15 9:10 ` Lucas Stach
2015-04-15 12:06 ` Sascha Hauer
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=1428650112.2182.1.camel@lynxeye.de \
--to=dev@lynxeye.de \
--cc=barebox@lists.infradead.org \
--cc=sebastian.hesselbarth@gmail.com \
/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