Linux-PHY Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: "Pali Rohár" <pali@kernel.org>
Cc: "Marek Behún" <kabel@kernel.org>,
	"linux-phy@lists.infradead.org" <linux-phy@lists.infradead.org>,
	"Damien Le Moal" <Damien.LeMoal@wdc.com>
Subject: Re: ARMADA espressobin SATA drive detection failure
Date: Fri, 26 Aug 2022 04:57:37 +0000	[thread overview]
Message-ID: <20220826045736.7ice6y3mruv7petg@shindev> (raw)
In-Reply-To: <20220825130443.ccjtbwvcjm7upvgy@pali>

On Aug 25, 2022 / 15:04, Pali Rohár wrote:

[...]

> Shinichiro, meanwhile, could you try following change on top of clean
> linux tree without any additional patches?

Thanks for caring this issue. Sure, I tried it on v5.18.16 and confirmed it
avoids the "ata1: SATA link down (SStatus 100 SControl 300)" message. My SSD was
detected as /dev/sda. It looks working as expected.

-- 
Shin'ichiro Kawasaki
-- 
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy

  reply	other threads:[~2022-08-26  4:57 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
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 [this message]
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=20220826045736.7ice6y3mruv7petg@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