linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Sergey Matyukevich <geomatsi@gmail.com>
Cc: devicetree@vger.kernel.org, Baruch Siach <baruch@tkos.co.il>,
	Gregory CLEMENT <gregory.clement@bootlin.com>,
	linux-arm-kernel@lists.infradead.org,
	Miquel Raynal <miquel.raynal@bootlin.com>
Subject: Re: [bug report] armada-8040-mcbin: 5.6-rc5 boot failure
Date: Mon, 13 Apr 2020 23:26:45 +0100	[thread overview]
Message-ID: <20200413222645.GT25745@shell.armlinux.org.uk> (raw)
In-Reply-To: <20200413220520.GA25917@curiosity>

On Tue, Apr 14, 2020 at 01:05:20AM +0300, Sergey Matyukevich wrote:
> 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 ?

I would strongly recommend upgrading the firmware in any case, because
of work I did (and submitted back through Jon @ SolidRun) to improve
the eye mask on the 10G Ethernet interfaces.  I'm using the 18.12
version.  Firmware build instructions can be found at:

https://developer.solid-run.com/knowledge-base/armada-8040-machiatobin-u-boot-and-atf/

I've booted 5.6 recently on a number of Armada 8040 based boards
without issue, likely all running the later firmware.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 10.2Mbps down 587kbps up

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-04-13 22:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-13 22:05 [bug report] armada-8040-mcbin: 5.6-rc5 boot failure Sergey Matyukevich
2020-04-13 22:26 ` Russell King - ARM Linux admin [this message]
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=20200413222645.GT25745@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=baruch@tkos.co.il \
    --cc=devicetree@vger.kernel.org \
    --cc=geomatsi@gmail.com \
    --cc=gregory.clement@bootlin.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --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).