From mboxrd@z Thu Jan  1 00:00:00 1970
From: Marek Vasut <marex@denx.de>
Date: Fri, 4 Jul 2014 17:44:05 +0200
Subject: [U-Boot] [PATCH 1/5] AHCI: Increase link timeout to 200ms
In-Reply-To: <1404487600.14796.39.camel@kazak.uk.xensource.com>
References: <1401554145.15871.100.camel@hastur.hellion.org.uk>
	<201407041658.10031.marex@denx.de>
	<1404487600.14796.39.camel@kazak.uk.xensource.com>
Message-ID: <201407041744.05319.marex@denx.de>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On Friday, July 04, 2014 at 05:26:40 PM, Ian Campbell wrote:
> On Fri, 2014-07-04 at 16:58 +0200, Marek Vasut wrote:
> > On Saturday, May 31, 2014 at 06:36:11 PM, Ian Campbell wrote:
> > > In 73545f75b66d "ahci: wait longer for link" I increased the
> > > timeout to 40ms based on the observed behaviour of a WD disk on a
> > > Cubietruck. Since then Karsten Merker and myself have both
> > > observed timeouts with HGST disks (Karsten on Cubietruck, me on
> > > Cubieboard2). Increasing the timeout to ~175ms fixes this, so go
> > > to 200ms for a bit of headroom.
> > > 
> > > Signed-off-by: Ian Campbell <ijc@hellion.org.uk>
> > > Cc: Karsten Merker <merker@debian.org>
> > 
> > Is there no way to poll for this condition instead of using an
> > ever-growing timeout?
> 
> This timeout is the maximum time to poll for. If the device is ready
> sooner (likely) then we'll notice that and carry one.

And if the device is never ready, then we will wait 200mS for nothing ?

Best regards,
Marek Vasut