linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Tejun Heo <tj@kernel.org>
Cc: ide <linux-ide@vger.kernel.org>,
	Nicolas.Mailhot@LaPoste.net, marcbowes@gmail.com,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH #upstream-fixes] ahci: add workaround for on-board 5723s on some gigabyte boards
Date: Wed, 12 Aug 2009 06:26:29 -0400	[thread overview]
Message-ID: <4A8298D5.9070100@pobox.com> (raw)
In-Reply-To: <4A77C760.1010300@kernel.org>

Tejun Heo wrote:
> Some gigabytes have on-board SIMG5723s connected to JMB ahcis.  These
> are used to implement hardware raid.  Unfortunately some firmware
> revisions on these 5723s don't bring the link down when all the
> downstream ports are unoccupied while not responding to reset protocol
> which makes libata think that there's device attached to the port but
> is not responding and retry.  This results in painfully wrong boot
> detection time for these ports when they're empty.
> 
> This patch quirks those boards such that ahci gives up after the
> initial timeout.  Combined with parallel probing, this gives quick
> enough probing and also is safe because SIMG5723 will respond to the
> first try if any of the downstream ports is occupied.
> 
> Signed-off-by: Tejun Heo <tj@kernel.org>
> Reported-by: Marc Bowes <marcbowes@gmail.com>
> Reported-by: Nicolas Mailhot <Nicolas.Mailhot@LaPoste.net>
> ---
>  drivers/ata/ahci.c |   76 ++++++++++++++++++++++++++++++++++++++++++++++++++---
>  1 file changed, 72 insertions(+), 4 deletions(-)

applied



      reply	other threads:[~2009-08-12 10:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-04  5:30 [PATCH #upstream-fixes] ahci: add workaround for on-board 5723s on some gigabyte boards Tejun Heo
2009-08-12 10:26 ` Jeff Garzik [this message]

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=4A8298D5.9070100@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=Nicolas.Mailhot@LaPoste.net \
    --cc=akpm@linux-foundation.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=marcbowes@gmail.com \
    --cc=tj@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;
as well as URLs for NNTP newsgroup(s).