mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Jeff Garzik <jeff@bloq.com>
Cc: Paul Menzel <pmenzel@molgen.mpg.de>,
	Damien Le Moal <damien.lemoal@opensource.wdc.com>,
	linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: ata: For what PHY was debounce delay introduced? (was: [PATCH v3 3/3] ahci: AMD A85 FCH (Hudson D4): Skip 200 ms debounce delay in `sata_link_resume()`)
Date: Fri, 7 Jan 2022 11:30:26 -1000	[thread overview]
Message-ID: <Ydiw8hxkNWDO2nW3@slm.duckdns.org> (raw)
In-Reply-To: <CAHy7=M10exWuVJtDVo+w36YKadY533GttzwrKxPnotHf8-JQnw@mail.gmail.com>

Hello,

On Wed, Jan 05, 2022 at 03:49:58PM -0500, Jeff Garzik wrote:
> On Tue, Jan 4, 2022 at 6:34 AM Paul Menzel <pmenzel@molgen.mpg.de> wrote:
> 
> > [cc: +jeff, +tejun]
> >
> > void sata_phy_reset(struct ata_port *ap)
> > {
> > […]
> >         /* wait for phy to become ready, if necessary */
> >         do {
> >                 msleep(200);
> >                 sstatus = scr_read(ap, SCR_STATUS);
> >                 if ((sstatus & 0xf) != 1)
> >                         break;
> >         } while (time_before(jiffies, timeout));
> > […]
> > }
> > ```
> >
> 
> The piix did not have SCRs, as I recall, so it wouldn't apply to those
> chips.   I don't recall further than that.
> 
> Presumably just give those early chips a "needs delay" quirk, and then
> start testing newer chips to make sure they survive an immediate bitbang?

I don't remember exactly but most likely the sata_sil chips, I think. But,
yeah, the way forward would be converting it to a quirk and gradually lift
them with tests.

Thanks and happy new year.

-- 
tejun

  parent reply	other threads:[~2022-01-07 21:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-29 16:11 [PATCH v3 1/3] PCI: Add device code for AMD FCH SATA Controller in AHCI mode Paul Menzel
2021-12-29 16:11 ` [PATCH v3 2/3] ahci: Use macro PCI_DEVICE_ID_AMD_HUDSON2_SATA_IDE Paul Menzel
2021-12-30  2:13   ` Damien Le Moal
2021-12-30 11:01     ` Paul Menzel
2021-12-31  0:50       ` Damien Le Moal
2021-12-30 13:35   ` Hannes Reinecke
2021-12-29 16:11 ` [PATCH v3 3/3] ahci: AMD A85 FCH (Hudson D4): Skip 200 ms debounce delay in `sata_link_resume()` Paul Menzel
2021-12-30  2:19   ` Damien Le Moal
2021-12-30 11:08     ` Paul Menzel
2021-12-31  0:52       ` Damien Le Moal
2021-12-31  7:08         ` Paul Menzel
2022-01-04  8:36           ` Damien Le Moal
2022-01-04  8:49             ` Paul Menzel
2022-01-04  9:08               ` Damien Le Moal
2022-01-04 11:34                 ` ata: For what PHY was debounce delay introduced? (was: [PATCH v3 3/3] ahci: AMD A85 FCH (Hudson D4): Skip 200 ms debounce delay in `sata_link_resume()`) Paul Menzel
     [not found]                   ` <CAHy7=M10exWuVJtDVo+w36YKadY533GttzwrKxPnotHf8-JQnw@mail.gmail.com>
2022-01-07 21:30                     ` Tejun Heo [this message]
2022-01-04  6:04   ` [PATCH v3 3/3] ahci: AMD A85 FCH (Hudson D4): Skip 200 ms debounce delay in `sata_link_resume()` Dmitry Torokhov
2021-12-30 19:21 ` [PATCH v3 1/3] PCI: Add device code for AMD FCH SATA Controller in AHCI mode Sergei Shtylyov

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=Ydiw8hxkNWDO2nW3@slm.duckdns.org \
    --to=tj@kernel.org \
    --cc=damien.lemoal@opensource.wdc.com \
    --cc=jeff@bloq.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmenzel@molgen.mpg.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

all inboxes | Powered by JetHome®