From: Baruch Siach <baruch@tkos.co.il>
To: u-boot@lists.denx.de
Subject: [PATCH 0/3] phy: marvell: cp110: fix Armada 8k rev B0 boot hang
Date: Tue, 20 Oct 2020 12:12:38 +0300 [thread overview]
Message-ID: <87o8kxtg55.fsf@tarshish> (raw)
In-Reply-To: <d0bf0ce1-26a0-06e7-2004-e62f4eb38bfb@denx.de>
Hi Stefan,
On Tue, Oct 20 2020, Stefan Roese wrote:
> On 18.10.20 16:11, Baruch Siach wrote:
>> Boot of Armada 8040 rev B0 hangs when U-Boot attempts to initialize the PCIe
>> serdes. Adapt patches from downstream Marvell tree that move serdes
>> initialization to ATF.
>>
>> This series requires upstream ATF version 2.1 or newer.
>
> Is there a way to detect if an older ATF is installed and print
> an error message (warning) in this case?
I see no way to detect ATF version using smc_call().
Downstream Marvell ATF have the required code[1] in the 18.12.2
release[2], which is based on ATF 1.5. This is the last ATF version from
Marvell that was released on github.
[1] https://github.com/MarvellEmbeddedProcessors/atf-marvell/commit/4db85ae088a5e2f51e9a5a671f531cb80a632067
[2] https://github.com/MarvellEmbeddedProcessors/atf-marvell/commits/atf-v1.5-armada-18.12
baruch
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
next prev parent reply other threads:[~2020-10-20 9:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-18 14:11 [PATCH 0/3] phy: marvell: cp110: fix Armada 8k rev B0 boot hang Baruch Siach
2020-10-18 14:11 ` [PATCH 1/3] phy: marvell: cp110: let the firmware configure the comphy Baruch Siach
2020-10-18 19:43 ` Marek Behun
2020-10-20 7:20 ` Stefan Roese
2020-10-18 14:11 ` [PATCH 2/3] phy: marvell: cp110: let the firmware configure comphy for PCIe Baruch Siach
2020-10-18 14:11 ` [PATCH 3/3] phy: marvell: cp110: update mode parameter for pcie power on calls Baruch Siach
2020-10-20 7:38 ` [PATCH 0/3] phy: marvell: cp110: fix Armada 8k rev B0 boot hang Stefan Roese
2020-10-20 9:12 ` Baruch Siach [this message]
2020-10-29 14:29 ` Stefan Roese
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=87o8kxtg55.fsf@tarshish \
--to=baruch@tkos.co.il \
--cc=u-boot@lists.denx.de \
/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