Linux-PHY Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: "Marek Behún" <kabel@kernel.org>
Cc: "Pali Rohár" <pali@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: Mon, 29 Aug 2022 00:20:10 +0000	[thread overview]
Message-ID: <20220829002009.q3ypdmybfbohk5pw@shindev> (raw)
In-Reply-To: <20220826140536.68eee458@dellmb>

On Aug 26, 2022 / 14:05, Marek Behún wrote:
> On Fri, 26 Aug 2022 05:00:20 +0000
> Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com> wrote:
> 
> > On Aug 26, 2022 / 00:15, Marek Behún wrote:
> > > On Thu, 25 Aug 2022 15:00:59 +0200
> > > Pali Rohár <pali@kernel.org> wrote:
> > >   
> > > > On Sunday 14 August 2022 01:10:50 Pali Rohár wrote:  
> > > > > On Saturday 13 August 2022 23:02:34 Shinichiro Kawasaki wrote:  
> > 
> > [...]
> > 
> > > > > Perfect! So the issue is with mvebu_a3700_comphy_reset() function.
> > > > > 
> > > > > This function is not in TF-A code and neither in my original kernel
> > > > > driver implementation (still available here):
> > > > > https://git.kernel.org/pub/scm/linux/kernel/git/pali/linux.git/commit/?h=phy-mvebu-a3700-comphy&id=4588902a3528195bcfdda9f9e1e14262a1955df1
> > > > > 
> > > > > Marek, this function mvebu_a3700_comphy_reset() was implemented by you.
> > > > > Could you please look at it, why you added this function and try to fix
> > > > > it? Is this function needed at all?    
> > > > 
> > > > PING? Any progress here?  
> > > 
> > > Not yet, sorry. Maybe we could do something like I am attaching, until
> > > I have time to play with it?
> > > 
> > > See attached file.  
> > 
> > Merek, thanks for the response. I applied the attached patch to v5.18.16 kernel
> > and observed the "ata1: SATA link down (SStatus 100 SControl 300)" message is
> > avoided. It looks working.
> > 
> 
> Hello Shinichiro,
> 
> would you be able to test another patch I am attaching, on clean kernel?
> Whether your disk works or not...

Sure, but unfortunately, it did not work. With "a3720-comphy-test-2.patch",
still the error "ata1: SATA link down (SStatus 100 SControl 300)" is printed,
and my SSD is not detected.

To be precise, this time I switched base kernel from v5.18.16 to v5.19.4, since
v5.18.y branch reached to EOL. With v5.19.4, my observation is consistent with
v5.18.16.

- v5.18.16:
   without patch: error "ata1: SATA link down (SStatus 100 SControl 300)"
   with "a3720-comphy-sata.patch": no ata error. my SSD detected

- v5.19.4:
   without patch: error "ata1: SATA link down (SStatus 100 SControl 300)"
   with "a3720-comphy-sata.patch": no ata error. my SSD detected
   with "a3720-comphy-test-2.patch": error "ata1: SATA link down (SStatus 100 SControl 300)"

-- 
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-29  0:20 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 [this message]
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=20220829002009.q3ypdmybfbohk5pw@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