linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: linuxppc-dev@lists.ozlabs.org, Olof Johansson <olof@lixom.net>
Subject: PASEMI: PCI_SCAN_ALL_PCIE_DEVS
Date: Wed, 14 Mar 2018 08:48:34 +0100	[thread overview]
Message-ID: <95560a8d-a75b-4ce1-8939-d2999e57e8fc@xenosoft.de> (raw)
In-Reply-To: <BD2DFDC2-07CF-41A8-9AAE-9D990EFF6360@xenosoft.de>

[-- Attachment #1: Type: text/plain, Size: 256 bytes --]

Hi All,

Please find attached the current pci.c patch. We use this patch on our 
P.A. Semi boards because we don't need to add 'pci=pcie_scan_all' to the 
kernel boot arguments.

Please add this patch to the official kernel source code.

Thanks,
Christian

[-- Attachment #2: pci.c.patch --]
[-- Type: text/x-patch, Size: 541 bytes --]

arch/powerpc/platforms/pasemi/pci.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/arch/powerpc/platforms/pasemi/pci.c b/arch/powerpc/platforms/pasemi/pci.c
index 5ff6108..ea54ed2 100644
--- a/arch/powerpc/platforms/pasemi/pci.c
+++ b/arch/powerpc/platforms/pasemi/pci.c
@@ -224,6 +224,8 @@ void __init pas_pci_init(void)
 		return;
 	}
 
+	pci_set_flags(PCI_SCAN_ALL_PCIE_DEVS);
+
 	for (np = NULL; (np = of_get_next_child(root, np)) != NULL;)
 		if (np->name && !strcmp(np->name, "pxp") && !pas_add_bridge(np))
 			of_node_get(np);

  reply	other threads:[~2018-03-14  7:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-12  5:21 PASEMI: PCI_SCAN_ALL_PCIE_DEVS Christian Zigotzky
2018-03-14  7:48 ` Christian Zigotzky [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-01-10 15:56 DPAA Ethernet problems with mainstream Linux kernels Jamie Krueger
2018-01-12 14:22 ` Madalin-cristian Bucur
2018-01-12 16:35   ` Jamie Krueger
2018-01-15 10:44     ` Madalin-cristian Bucur
2018-02-26 23:11       ` PASEMI: PCI_SCAN_ALL_PCIE_DEVS Christian Zigotzky

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=95560a8d-a75b-4ce1-8939-d2999e57e8fc@xenosoft.de \
    --to=chzigotzky@xenosoft.de \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=olof@lixom.net \
    /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).