Re: [PATCH 1/2] tx4938ide: Check minimum cycle time and SHWT range

To:	Sergei Shtylyov <sshtylyov@ru.mvista.com>
Subject:	Re: [PATCH 1/2] tx4938ide: Check minimum cycle time and SHWT range
From:	Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Date:	Wed, 29 Oct 2008 20:12:19 +0100
Cc:	Atsushi Nemoto <anemo@mba.ocn.ne.jp>, linux-mips@linux-mips.org, linux-ide@vger.kernel.org, ralf@linux-mips.org
Dkim-signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :user-agent:cc:references:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:message-id; bh=vpLr9Xve0Fc6K+HiOQ7odtm2v9h8lfpXavFwqPBTWXY=; b=fwQD/c5jrvR7NktipmnvXSbUWd5yIXhnWYeDjXlKKictxl0doQtWIqstlkMX4GiAp8 KbIL8NvE5N4Gw8rmb9NC+ZocZ50FEPAP4NmpXdCm12zi/8g0Io9nGxrz76RUAmdVRFgr 94AW4Ousr4xVN1kDTpsMXXLK1Kj6zABNtdug4=
Domainkey-signature:	a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:cc:references:in-reply-to :mime-version:content-type:content-transfer-encoding :content-disposition:message-id; b=QquMAmvxpiKabR/mQfW+L13KpfYclQt+wMOPsjj1DWRrC9wI2d5RuS6AQXSObsQqCF YIWAEmqsRnO2B9SPaxTKeyhu8uPpprvCmAp4N8itbBQjvzcG8hya7ah5EseUuvi68SAI HYEPExD+NprAUiAaacHYCKZNO/gdRmp/KVpG4=
In-reply-to:	<49064ACA.20200@ru.mvista.com>
Original-recipient:	rfc822;linux-mips@linux-mips.org
References:	<20081027.223913.128619425.anemo@mba.ocn.ne.jp> <20081027.235224.82088530.anemo@mba.ocn.ne.jp> <49064ACA.20200@ru.mvista.com>
Sender:	linux-mips-bounce@linux-mips.org
User-agent:	KMail/1.9.10

On Tuesday 28 October 2008, Sergei Shtylyov wrote:
> Hello.
> 
> Atsushi Nemoto wrote:
> 
> > From: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
> > Subject: [PATCH] tx4938ide: Check minimum cycle time and SHWT range (v2)
> >
> > SHWT value is used as address valid to -CSx assertion and -CSx to -DIOx
> > assertion setup time, and contrarywise, -DIOx to -CSx release and -CSx
> > release to address invalid hold time, so it actualy applies 4 times and
> > so constitutes -DIOx recovery time.  Check requirement of the recovery
> > time and cycle time.  Also check SHWT maximum value.
> >
> > Suggested-by: Sergei Shtylyov <sshtylyov@ru.mvista.com>
> > Signed-off-by: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
> >   
> 
> Acked-by: Sergei Shtylyov <sshtylyov@ru.mvista.com>

applied

<Prev in Thread]	Current Thread	[Next in Thread>
[PATCH 1/2] tx4938ide: Check minimum cycle time and SHWT range, Atsushi Nemoto Re: [PATCH 1/2] tx4938ide: Check minimum cycle time and SHWT range, Sergei Shtylyov Re: [PATCH 1/2] tx4938ide: Check minimum cycle time and SHWT range, Atsushi Nemoto Re: [PATCH 1/2] tx4938ide: Check minimum cycle time and SHWT range, Sergei Shtylyov Re: [PATCH 1/2] tx4938ide: Check minimum cycle time and SHWT range, Bartlomiej Zolnierkiewicz <=

Previous by Date:	Re: [PATCH 06/36] Add Cavium OCTEON processor CSR definitions, Christoph Hellwig
Next by Date:	Re: [PATCH 2/2] tx4938ide: Do not call devm_ioremap for whole 128KB, Bartlomiej Zolnierkiewicz
Previous by Thread:	Re: [PATCH 1/2] tx4938ide: Check minimum cycle time and SHWT range, Sergei Shtylyov
Next by Thread:	[PATCH 2/2] tx4938ide: Do not call devm_ioremap for whole 128KB, Atsushi Nemoto
Indexes:	[Date] [Thread] [Top] [All Lists]