From: Andre Heider <a.heider@gmail.com>
To: u-boot@lists.denx.de
Subject: [PATCH u-boot-marvell] arm64: dts: armada-3720-espressobin: fix COMPHY nodes
Date: Fri, 28 Aug 2020 16:59:30 +0200 [thread overview]
Message-ID: <3db3c998-666e-6d27-d00a-2a1fd99a5b3f@gmail.com> (raw)
In-Reply-To: <c7d83354-6be3-3d53-775f-0eea7f619d50@gmail.com>
On 28/08/2020 10:18, Andre Heider wrote:
> Hi Marek,
>
> On 19/08/2020 11:57, Marek Beh?n wrote:
>> This commit fixes initialization of COMPHY on EspressoBin.
>>
>> Commit 22f418935be4 ("phy: marvell: a3700: Use comphy_mux on Armada
>> 37xx.") introduced usage of comphy_mux on Armada 37xx comphy driver.
>> The lanes are defined in comphy_a3700.c as described in functional
>> specification, that is:
>> ?? lane 0 is SGMII1 or USB3
>> ?? lane 1 is PCIe or SGMII0
>> ?? lane 2 is SATA or USB3
>>
>> But the DTS for EspressoBin configures PCIe on lane 0 and USB3 on
>> lane 1, which is wrong in the sense of the specification and doesn't
>> work with the comphy_mux code, which is 2 years now (the aardvark driver
>> causes synchronous abort in U-Boot).
>>
>> It worked till the above mentioned commit, because the code for powering
>> up PCIe PHY doesn't work with lane number at all, and the code for
>> powering up USB3 PHY works differently only if USB3 is on lane 2, ie.
>> the check goes like:
>> ?? if (lane == 2)
>> ???? something
>> ?? else
>> ???? something else
>> so it does not differentiate between lanes 0 and 1.
>>
>> In the future I shall post patches that remove the comphy_a3700 driver
>> and add comphy driver which uses calls to ATF, like Linux' driver does.
>> This will have the advantage of same DTS bindings as Linux', but till
>> this is done, we need this patch.
>>
>> Signed-off-by: Marek Beh?n <marek.behun@nic.cz>
>> Tested-by: Pali Roh?r <pali@kernel.org>
>> Cc: Stefan Roese <sr@denx.de>
>
> now that I have a working mainline firmware, I think I have a related
> problem: my sata ssd doesn't get detected, I just get this:
>
> TIM-1.0
> WTMI-devel-18.12.1-
> WTMI: system early-init
> CPU VDD voltage default value: 1.108V
> NOTICE:? Booting Trusted Firmware
> NOTICE:? BL1: v2.3(): (Marvell-devel-18.12.0)
> NOTICE:? BL1: Built : 06:12:46, Aug 26 2020
> NOTICE:? BL1: Booting BL2
> NOTICE:? BL2: v2.3(): (Marvell-devel-18.12.0)
> NOTICE:? BL2: Built : 06:12:46, Aug 26 2020
> NOTICE:? BL1: Booting BL31
> NOTICE:? BL31: v2.3(): (Marvell-devel-18.12.0)
> NOTICE:? BL31: Built : 06:12:46
>
> U-Boot 2020.07 (Aug 26 2020 - 06:12:46 +0000)
>
> DRAM:? 1 GiB
> Comphy-0: USB3_HOST0??? 5 Gbps
> Comphy-1: PEX0????????? 2.5 Gbps
> Comphy-2: SATA0???????? 5 Gbps
> SATA link 0 timeout.
>
> Any idea what's missing here? Do you think this may also be comphy related?
>
> Please cc: me on your comphy/atf patches, I'd be willing to test those!
Nevermind, Pali figured it out:
https://patchwork.ozlabs.org/project/uboot/patch/20200828145629.540954-1-a.heider at gmail.com/
Regards,
Andre
next prev parent reply other threads:[~2020-08-28 14:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 9:57 [PATCH u-boot-marvell] arm64: dts: armada-3720-espressobin: fix COMPHY nodes Marek Behún
2020-08-19 10:10 ` [EXT] " Kostya Porotchkin
2020-08-19 10:33 ` Stefan Roese
2020-08-26 7:12 ` Andre Heider
2020-08-28 8:18 ` Andre Heider
2020-08-28 14:59 ` Andre Heider [this message]
2020-08-30 6:38 ` Andre Heider
2020-08-30 22:57 ` Marek Behun
2020-08-31 13:02 ` 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=3db3c998-666e-6d27-d00a-2a1fd99a5b3f@gmail.com \
--to=a.heider@gmail.com \
--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