From: Sergey Matyukevich <geomatsi@gmail.com>
To: Russell King <linux@armlinux.org.uk>,
Miquel Raynal <miquel.raynal@bootlin.com>,
linux-arm-kernel@lists.infradead.org
Cc: devicetree@vger.kernel.org, Baruch Siach <baruch@tkos.co.il>,
Gregory CLEMENT <gregory.clement@bootlin.com>
Subject: [bug report] armada-8040-mcbin: 5.6-rc5 boot failure
Date: Tue, 14 Apr 2020 01:05:20 +0300 [thread overview]
Message-ID: <20200413220520.GA25917@curiosity> (raw)
Hi Russel, Miquel, and all,
MacchiatoBin Double-shot board fails to boot v5.6-rc5 kernel properly:
USB, PCIe, and ethernet interfaces are not enabled. Before that I have
been running v5.3 kernel w/o any noticeable issues.
In brief, USB and PCIe devices are not detected, ethernet PHY fails
to initialize with the following warnings:
[ 2.444150] mvebu-comphy f4120000.phy: unsupported SMC call, try updating your firmware
[ 2.452191] mvebu-comphy f4120000.phy: Firmware could not configure PHY 0 with mode 15 (ret: -1), trying legacy method
[ 2.474615] mvpp2 f4000000.ethernet eth2: Using firmware node mac address ...
[ 2.484420] mvebu-comphy f4120000.phy: unsupported SMC call, try updating your firmware
After quick bisection of the board dts files, I came to the following results:
- USB works again after reverting the following two commits:
-- 96018a6fafb1 ("arm64: dts: marvell: Convert 7k/8k usb-phy properties to phy-supply")
-- 01d0deba28f6 ("arm64: dts: marvell: Add 7k/8k PHYs in USB3 nodes")
- PCIe works again after reverting armada-8040-mcbin.dtsi parts of the
following two commits:
-- 1399672e48b5 ("arm64: dts: marvell: Drop PCIe I/O ranges from CP11x file")
-- ce55522c035e ("arm64: dts: marvell: Add 7k/8k PHYs in PCIe nodes")
- ethernet: not yet...
However looking at firmware version complaints, I guess that the actual
reason of all those issues could be in ATF version rather than in the
latest DTS changes. Probably I am using ATF version which is too old
to work with up-to-date kernel: armada-17.10.3 from atf-marvell
repository on github. If this is indeed the actual root cause of all
the issues, then could you please recommend a preferable ATF version
to test with ?
Regards,
Sergey
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-04-13 22:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 22:05 Sergey Matyukevich [this message]
2020-04-13 22:26 ` [bug report] armada-8040-mcbin: 5.6-rc5 boot failure Russell King - ARM Linux admin
2020-04-14 16:03 ` Sergey Matyukevich
2020-04-14 16:08 ` Willy Tarreau
2020-04-14 16:55 ` Russell King - ARM Linux admin
2020-04-14 17:17 ` Willy Tarreau
2020-04-14 21:52 ` Sergey Matyukevich
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=20200413220520.GA25917@curiosity \
--to=geomatsi@gmail.com \
--cc=baruch@tkos.co.il \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=miquel.raynal@bootlin.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;
as well as URLs for NNTP newsgroup(s).