From: Lucas Stach <l.stach@pengutronix.de>
To: Andrey Smirnov <andrew.smirnov@gmail.com>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: i.MX6 PCIe support
Date: Tue, 01 Dec 2015 11:10:22 +0100 [thread overview]
Message-ID: <1448964622.8275.40.camel@pengutronix.de> (raw)
In-Reply-To: <CAHQ1cqFvLA2UnRBcsdUk05-4OJP33D1E=R7i0tkBtrGX_SvoFQ@mail.gmail.com>
Hi Andrey,
Am Montag, den 30.11.2015, 10:56 -0800 schrieb Andrey Smirnov:
> Hi All,
>
> I am working on adding EEPROM programming capabilities to e1000 driver
> on a custom i.MX6Q (automotive) board with i210 (8086:1531) connected
> over PCIe link. Unfortunately I am observing some bad/unexpected
> behavior that might indicate PCIe issues.
>
> What I am seeing is device(i210) enumerating on PCIe bus, however any
> accesses to its registers via its memory "window" result in either
> 0xFFFFFFFF or 0xDEADBEEF. I tried accessing various PCIe configuration
> registers of that device and it seem to work fine (as a part of that
> test I read out some AER registers and they didn't indicate presence
> of any PCIe link related errors).
>
> However when I boot Linux kernel (with 'igb' driver patched to
> recognize 8086:1531 VID:PID) on that board and run 'eepromARMtool'
> (Intel provided EEPROM programming tool) I can see it reading various
> registers correctly
>
> My questions are:
> - Is anyone currently using i.MX6 PCIe driver in 'next' branch?
I didn't try the latest revision, but with v2015.10.0 PCIe on i.MX6 was
working fine.
> - Has anyone seen similar behavior on this particular controller
> and discovered the root cause?
>
The symptoms you describe do look to me like the firmware on the i210
device doesn't get initialized. Unfortunately I don't have any specific
pointers where to start searching for the root cause.
Regards,
Lucas
--
Pengutronix e.K. | Lucas Stach |
Industrial Linux Solutions | http://www.pengutronix.de/ |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2015-12-01 10:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 18:56 Andrey Smirnov
2015-12-01 10:10 ` Lucas Stach [this message]
2015-12-07 6:03 ` Andrey Smirnov
2015-12-07 9:28 ` Lucas Stach
2015-12-08 4:24 ` Andrey Smirnov
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=1448964622.8275.40.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=andrew.smirnov@gmail.com \
--cc=barebox@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