From: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: "Pali Rohár" <pali@kernel.org>
Cc: "linux-phy@lists.infradead.org" <linux-phy@lists.infradead.org>,
"kabel@kernel.org" <kabel@kernel.org>,
Damien Le Moal <Damien.LeMoal@wdc.com>
Subject: Re: ARMADA espressobin SATA drive detection failure
Date: Sat, 13 Aug 2022 12:47:30 +0000 [thread overview]
Message-ID: <20220813124729.qondfc7z5eoeoq7p@shindev> (raw)
In-Reply-To: <20220813120108.vaiwnzhofz6hy5kc@pali>
On Aug 13, 2022 / 14:01, Pali Rohár wrote:
> On Saturday 13 August 2022 11:53:39 Shinichiro Kawasaki wrote:
> > On Aug 13, 2022 / 11:32, Pali Rohár wrote:
> > > On Saturday 13 August 2022 01:35:35 Shinichiro Kawasaki wrote:
> >
> > [...]
> >
> > > Ok, thanks for testing. It looks like that reset code has some issues.
> > >
> > > Could you please test this change?
> > >
> > > @@ -1393,7 +1436,8 @@ static int mvebu_a3700_comphy_probe(struct platform_device *pdev)
> > > * To avoid relying on the bootloader/firmware configuration,
> > > * power off all comphys.
> > > */
> > > - mvebu_a3700_comphy_reset(phy);
> > > +// mvebu_a3700_comphy_reset(phy);
> > > + mvebu_a3700_comphy_power_off(phy);
> > > lane->needs_reset = false;
> > > }
> > >
> > >
> > > It should replace reset code by power off at beginning / probe time.
> >
> > This change also avoided the "ata1: SATA link down (SStatus 0 SControl 300)"
> > message, and my SSD was detected as /dev/sda. Good symptoms for me. FYI, I
> > attach the console log with this change. (This time, following messages were
> > printed. Not sure if they are important or not.)
> >
> > [ 2.937376] mvebu-a3700-comphy d0018300.phy: invalid COMPHY mode
> > [ 2.943581] mvebu-a3700-comphy d0018300.phy: invalid COMPHY mode
> > [ 2.949679] mvebu-a3700-comphy d0018300.phy: invalid COMPHY mode
>
> Those errors are important, it means that power_off did nothing and was
> skipped. So test did nothing.
>
> Could you please replace mvebu_a3700_comphy_power_off implementation
> with this one and try it again?
>
> static int mvebu_a3700_comphy_power_off(struct phy *phy)
> {
> struct mvebu_a3700_comphy_lane *lane = phy_get_drvdata(phy);
>
> switch (lane->id) {
> case 0:
> mvebu_a3700_comphy_usb3_power_off(lane);
> mvebu_a3700_comphy_ethernet_power_off(lane);
> return 0;
> case 1:
> mvebu_a3700_comphy_pcie_power_off(lane);
> mvebu_a3700_comphy_ethernet_power_off(lane);
> return 0;
> case 2:
> mvebu_a3700_comphy_usb3_power_off(lane);
> mvebu_a3700_comphy_sata_power_off(lane);
> return 0;
> default:
> dev_err(lane->dev, "invalid COMPHY mode\n");
> return -EINVAL;
> }
> }
Thanks, but this hunk failed to compile with the error below.
rivers/phy/marvell/phy-mvebu-a3700-comphy.c: In function 'mvebu_a3700_comphy_power_off':
drivers/phy/marvell/phy-mvebu-a3700-comphy.c:1229:17: error: implicit declaration of function 'mvebu_a3700_comphy_usb3_power_off'; did you mean 'mvebu_a3700_comphy_usb3_power_on'? [-Werror=implicit-function-declaration]
1229 | mvebu_a3700_comphy_usb3_power_off(lane);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| mvebu_a3700_comphy_usb3_power_on
cc1: some warnings being treated as errors
Do I need to add mvebu_a3700_comphy_usb3_power_off() function?
I suspend this work here today. Will resume it tomorrow. Thank you for your
actions so far. Wish this issue gets resolved soon.
--
Shin'ichiro Kawasaki
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2022-08-13 12:47 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 12:41 ARMADA espressobin SATA drive detection failure Shinichiro Kawasaki
2022-05-31 14:00 ` 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 [this message]
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=20220813124729.qondfc7z5eoeoq7p@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