From: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: "linux-phy@lists.infradead.org" <linux-phy@lists.infradead.org>,
"pali@kernel.org" <pali@kernel.org>,
"kabel@kernel.org" <kabel@kernel.org>
Cc: Damien Le Moal <Damien.LeMoal@wdc.com>
Subject: ARMADA espressobin SATA drive detection failure
Date: Tue, 31 May 2022 12:41:59 +0000 [thread overview]
Message-ID: <20220531124159.3e4lgn2v462irbtz@shindev> (raw)
Hello Pali, Marek,
I have an ARMADA espressobin board, and I'm setting up SATA drive test
environment on it. Using that board, I observe that SATA drives are not
detected after merging two commits [1]. They were merged in the kernel at
v5.18-rc1. With v5.17 kernel, the SATA drives were successfully detected.
Reverting the commits from v5.18, SATA drives can be detected.
[1] ee995101fde6 ("Revert "ata: ahci: mvebu: Make SATA PHY optional for Armada 3720"")
934337080c6c ("phy: marvell: phy-mvebu-a3700-comphy: Add native kernel implementation")
FYI, here I share related kernel messsages:
$ dmesg | grep -e ata -e mvebu
[ 4.007130] ahci-mvebu d00e0000.sata: supply ahci not found, using dummy regulator
[ 4.014963] ahci-mvebu d00e0000.sata: supply phy not found, using dummy regulator
[ 4.022596] ahci-mvebu d00e0000.sata: supply target not found, using dummy regulator
[ 4.031123] ahci-mvebu d00e0000.sata: AHCI 0001.0300 32 slots 1 ports 6 Gbps 0x1 impl platform mode
[ 4.040180] ahci-mvebu d00e0000.sata: flags: ncq sntf led only pmp fbs pio slum part sxs
[ 4.050150] scsi host0: ahci-mvebu
[ 4.053949] ata1: SATA max UDMA/133 mmio [mem 0xd00e0000-0xd00e0177] port 0x100 irq 30
[ 4.388934] ata1: SATA link down (SStatus 0 SControl 300)
[ 5.239165] EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Quota mode: none.
[ 10.751378] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 45.727407] ata1: SATA link down (SStatus 100 SControl 300) (... I connected a drive to the SATA port)
[ 46.497413] ata1: SATA link down (SStatus 100 SControl 300)
[ 47.267411] ata1: SATA link down (SStatus 100 SControl 300)
[ 48.047412] ata1: SATA link down (SStatus 100 SControl 300)
[ 48.827416] ata1: SATA link down (SStatus 100 SControl 300)
[ 49.597411] ata1: SATA link down (SStatus 100 SControl 300)
[ 50.577414] ata1: SATA link down (SStatus 100 SControl 300)
[ 51.357409] ata1: SATA link down (SStatus 100 SControl 300)
[ 52.587418] ata1: SATA link down (SStatus 100 SControl 300)
[ 53.367419] ata1: SATA link down (SStatus 100 SControl 300)
[ 54.147413] ata1: SATA link down (SStatus 100 SControl 300)
[ 54.917412] ata1: SATA link down (SStatus 100 SControl 300)
[ 55.697410] ata1: SATA link down (SStatus 100 SControl 300)
[ 56.477411] ata1: SATA link down (SStatus 100 SControl 300)
[ 57.247415] ata1: SATA link down (SStatus 100 SControl 300)
[ 58.017413] ata1: SATA link down (SStatus 100 SControl 300)
[ 58.797412] ata1: SATA link down (SStatus 0 SControl 300) (... I removed the drive from the SATA port)
As shown above, the message: "ata1: SATA link down (SStatus 100 SControl 300)"
is repeated. It looks like the function mvebu_a3700_comphy_sata_power_on()
fails to set up SATA phy correctly, but I'm not sure how to investigate further.
Could you advise next action to fix this issue?
--
Shin'ichiro Kawasaki
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next reply other threads:[~2022-05-31 12:42 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 12:41 Shinichiro Kawasaki [this message]
2022-05-31 14:00 ` ARMADA espressobin SATA drive detection failure Marek Behún
2022-06-06 1:57 ` Shinichiro Kawasaki
2022-08-09 9:42 ` Pali Rohár
2022-08-10 10:36 ` Shinichiro Kawasaki
2022-08-12 4:56 ` Shinichiro Kawasaki
2022-08-12 8:20 ` Pali Rohár
2022-08-12 12:00 ` Shinichiro Kawasaki
2022-08-12 12:44 ` Pali Rohár
2022-08-12 13:55 ` Pali Rohár
2022-08-13 0:02 ` Shinichiro Kawasaki
2022-08-13 0:15 ` Pali Rohár
2022-08-13 1:00 ` Shinichiro Kawasaki
2022-08-13 1:03 ` Pali Rohár
2022-08-13 1:35 ` Shinichiro Kawasaki
2022-08-13 9:32 ` Pali Rohár
2022-08-13 11:53 ` Shinichiro Kawasaki
2022-08-13 12:01 ` Pali Rohár
2022-08-13 12:47 ` Shinichiro Kawasaki
2022-08-13 12:50 ` Pali Rohár
2022-08-13 23:02 ` Shinichiro Kawasaki
2022-08-13 23:10 ` Pali Rohár
2022-08-25 13:00 ` Pali Rohár
2022-08-25 22:15 ` Marek Behún
2022-08-26 5:00 ` Shinichiro Kawasaki
2022-08-26 12:05 ` Marek Behún
2022-08-29 0:20 ` Shinichiro Kawasaki
2022-08-29 8:33 ` Pali Rohár
2022-08-26 7:28 ` Pali Rohár
2022-08-25 13:04 ` Pali Rohár
2022-08-26 4:57 ` Shinichiro Kawasaki
2022-08-26 7:34 ` Pali Rohár
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=20220531124159.3e4lgn2v462irbtz@shindev \
--to=shinichiro.kawasaki@wdc.com \
--cc=Damien.LeMoal@wdc.com \
--cc=kabel@kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=pali@kernel.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