From: phil@nwl.cc (Phil Sutter)
To: linux-arm-kernel@lists.infradead.org
Subject: Broken PCIe on Synology DS414
Date: Sat, 5 Mar 2016 15:36:31 +0100 [thread overview]
Message-ID: <20160305143445.827496739A@mail.nwl.cc> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Commit c466d997bb160 ("ARM: mvebu: define crypto SRAM ranges for all
armada-xp boards") breaks PCIe on the MV78230 based Synology DS414. The
kernel does not complain, but 'lspci' does not show a single device.
Reverting this commit cures vanilla 4.5-rc6 again for me.
Seems like the ranges declared for crypto SRAM conflict with PCIe
controller ones in some way. Looking at the DT files, all MV78230 based
devices should be affected, not just the DS414.
Is this a known problem? Please let me know if there is anything I can
do to further analyze the issue.
Thanks, Phil
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iEYEARECAAYFAlba7uwACgkQnMPprxY1hCf8tACcDc1uAjGIw9Q06hxZ6sz3hQf9
19EAn355YCXKamlXK3ir/Sh/fhtvZpew
=71Sh
-----END PGP SIGNATURE-----
next reply other threads:[~2016-03-05 14:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-05 14:36 Phil Sutter [this message]
2016-03-08 13:45 ` Broken PCIe on Synology DS414 Thomas Petazzoni
2016-03-08 14:04 ` Phil Sutter
2016-03-08 14:48 ` Thomas Petazzoni
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=20160305143445.827496739A@mail.nwl.cc \
--to=phil@nwl.cc \
--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;
as well as URLs for NNTP newsgroup(s).