From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755865Ab0ARSXo (ORCPT ); Mon, 18 Jan 2010 13:23:44 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755846Ab0ARSXm (ORCPT ); Mon, 18 Jan 2010 13:23:42 -0500 Received: from mail-ew0-f219.google.com ([209.85.219.219]:42957 "EHLO mail-ew0-f219.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754469Ab0ARSXh (ORCPT ); Mon, 18 Jan 2010 13:23:37 -0500 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:message-id:content-type:content-transfer-encoding; b=rd9sg2zrR0sG8lToH9AblYsDwxKRtZL+clxfXnYusaw3t4fBDwspb3Tyx/W1HQsR9y U8/aiCQn354kkREM3wHWRyWbeJB05WGJrBXIcs07nhk+iwkN04M+U9J+dvfaW0iF9K3J EQZDXYdbOcRxx37z8em3Ld3g7JMUB1FyMXJ2Q= From: Bartlomiej Zolnierkiewicz To: Alan Cox Subject: Re: [PATCH 04/64] pata_amd: remove bogus code from timing_setup() Date: Mon, 18 Jan 2010 19:18:45 +0100 User-Agent: KMail/1.12.2 (Linux/2.6.31.8-0.1-desktop; KDE/4.3.1; x86_64; ; ) Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org References: <20100118171349.14623.90030.sendpatchset@localhost> <20100118171420.14623.85263.sendpatchset@localhost> <20100118175037.23727d64@lxorguk.ukuu.org.uk> In-Reply-To: <20100118175037.23727d64@lxorguk.ukuu.org.uk> MIME-Version: 1.0 Message-Id: <201001181918.45314.bzolnier@gmail.com> Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Monday 18 January 2010 06:50:37 pm Alan Cox wrote: > On Mon, 18 Jan 2010 18:14:20 +0100 > Bartlomiej Zolnierkiewicz wrote: > > > From: Bartlomiej Zolnierkiewicz > > Subject: [PATCH] pata_amd: remove bogus code from timing_setup() > > > > DMA modes don't have 8-bit timings. s/timings/data timings/ [ though it should be obvious from the context ] > If you are in a DMA based mode then you have 8bit timings for writes to > the non data registers. You can get an 8bit timed access to the other > drive even in DMA mode. Sorry but this confuses taskfile timings (which are always PIO mode based timings) with data timings (the removed code deals with the latter only).. also please refer to ata_timings[] in drivers/ata/libata-core.c (columns 3, 4 and 5 are the ones to look at): static const struct ata_timing ata_timing[] = { /* { XFER_PIO_SLOW, 120, 290, 240, 960, 290, 240, 0, 960, 0 }, */ { XFER_PIO_0, 70, 290, 240, 600, 165, 150, 0, 600, 0 }, { XFER_PIO_1, 50, 290, 93, 383, 125, 100, 0, 383, 0 }, { XFER_PIO_2, 30, 290, 40, 330, 100, 90, 0, 240, 0 }, { XFER_PIO_3, 30, 80, 70, 180, 80, 70, 0, 180, 0 }, { XFER_PIO_4, 25, 70, 25, 120, 70, 25, 0, 120, 0 }, { XFER_PIO_5, 15, 65, 25, 100, 65, 25, 0, 100, 0 }, { XFER_PIO_6, 10, 55, 20, 80, 55, 20, 0, 80, 0 }, { XFER_SW_DMA_0, 120, 0, 0, 0, 480, 480, 50, 960, 0 }, { XFER_SW_DMA_1, 90, 0, 0, 0, 240, 240, 30, 480, 0 }, { XFER_SW_DMA_2, 60, 0, 0, 0, 120, 120, 20, 240, 0 }, { XFER_MW_DMA_0, 60, 0, 0, 0, 215, 215, 20, 480, 0 }, { XFER_MW_DMA_1, 45, 0, 0, 0, 80, 50, 5, 150, 0 }, { XFER_MW_DMA_2, 25, 0, 0, 0, 70, 25, 5, 120, 0 }, { XFER_MW_DMA_3, 25, 0, 0, 0, 65, 25, 5, 100, 0 }, { XFER_MW_DMA_4, 25, 0, 0, 0, 55, 20, 5, 80, 0 }, /* { XFER_UDMA_SLOW, 0, 0, 0, 0, 0, 0, 0, 0, 150 }, */ { XFER_UDMA_0, 0, 0, 0, 0, 0, 0, 0, 0, 120 }, { XFER_UDMA_1, 0, 0, 0, 0, 0, 0, 0, 0, 80 }, { XFER_UDMA_2, 0, 0, 0, 0, 0, 0, 0, 0, 60 }, { XFER_UDMA_3, 0, 0, 0, 0, 0, 0, 0, 0, 45 }, { XFER_UDMA_4, 0, 0, 0, 0, 0, 0, 0, 0, 30 }, { XFER_UDMA_5, 0, 0, 0, 0, 0, 0, 0, 0, 20 }, { XFER_UDMA_6, 0, 0, 0, 0, 0, 0, 0, 0, 15 }, { 0xFF } }; -- Bartlomiej Zolnierkiewicz