From: slash.tmp@free.fr (Mason)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/2] Tango PCIe controller support
Date: Thu, 30 Mar 2017 22:56:58 +0200 [thread overview]
Message-ID: <1561c381-bfa7-6e4d-a016-8ad7293a60ce@free.fr> (raw)
In-Reply-To: <5309e718-5813-5b79-db57-9d702b50d0f9@sigmadesigns.com>
On 29/03/2017 13:11, Marc Gonzalez wrote:
> PCI: Add tango MSI controller support
> PCI: Add tango PCIe host bridge support
I've run into an issue.
If I boot the system with earlyprintk enabled (as I've
been doing throughout my dev), things work as expected.
But if I boot with earlyprintk disabled, then the system
does not "see" the PCIe board, because reading the vendor
ID returns 0xffffffff.
What we think is happening, is that when earlyprintk is
disabled, the system proceeds much faster through the
various inits, and the PCIe init happens when PCIe
link training has not completed yet.
If that is the case, then it seems I would need to check
the link state in my probe function.
Or would there be some other solution I haven't thought
about?
Regards.
next prev parent reply other threads:[~2017-03-30 20:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 11:11 [PATCH v3 0/2] Tango PCIe controller support Marc Gonzalez
2017-03-29 11:29 ` [PATCH v3 1/2] PCI: Add tango MSI " Marc Gonzalez
2017-03-29 12:29 ` Marc Zyngier
2017-03-29 13:16 ` Mason
2017-03-29 15:50 ` Mason
2017-03-29 11:34 ` [PATCH v3 2/2] PCI: Add tango PCIe host bridge support Marc Gonzalez
2017-03-29 12:19 ` Robin Murphy
2017-03-29 12:53 ` Mason
2017-03-29 14:33 ` Robin Murphy
2017-03-29 14:38 ` David Laight
2017-03-30 12:09 ` kbuild test robot
2017-04-03 14:51 ` Rob Herring
2017-04-09 13:09 ` Mason
2017-03-30 20:56 ` Mason [this message]
2017-03-31 22:05 ` [PATCH v3 0/2] Tango PCIe controller support Mason
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=1561c381-bfa7-6e4d-a016-8ad7293a60ce@free.fr \
--to=slash.tmp@free.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox