public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linux-kernel@vger.kernel.org, bzolnier@gmail.com
Subject: Re: Parallel ATA with libata status with the patches I'm working on
Date: Fri, 4 Nov 2005 23:10:48 +0000	[thread overview]
Message-ID: <20051104231048.GD12026@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1131111667.26925.31.camel@localhost.localdomain>

On Fri, Nov 04, 2005 at 01:41:06PM +0000, Alan Cox wrote:
> While writing the new sl82c05 driver I noticed a real nasty lurking in
> the old code. According to the errata docs you have to reset the DMA
> engine every transfer to work around chip errata. It also says that this
> resets any other ATA transfer in progress.
> 
> If both channels are in use there is no locking between the channels to
> stop a reset on one channel as DMA begins making a mess of the other
> channel. Looks like serialize should be set on the driver ?

Possibly, though benh needs to comment.  (I think benh has the only
hardware which has the possibility of both channels - the NetWinder
only has one channel with one disk.)

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

  reply	other threads:[~2005-11-04 23:10 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-03 14:54 Parallel ATA with libata status with the patches I'm working on Alan Cox
2005-11-03 14:48 ` Russell King
2005-11-03 15:02   ` Bartlomiej Zolnierkiewicz
2005-11-03 15:28     ` David S. Miller
2005-11-03 15:48       ` Bartlomiej Zolnierkiewicz
2005-11-03 16:27         ` Alan Cox
2005-11-03 15:56     ` Alan Cox
2005-11-03 20:55     ` Krzysztof Halasa
2005-11-03 21:29       ` Bartlomiej Zolnierkiewicz
2005-11-03 22:29         ` Krzysztof Halasa
2005-11-03 22:48           ` Bartlomiej Zolnierkiewicz
2005-11-03 22:54         ` Alan Cox
2005-11-04  1:30           ` Rogério Brito
2005-11-04 13:38             ` Alan Cox
2005-11-04 13:41             ` Alan Cox
2005-11-04 23:10               ` Russell King [this message]
2005-11-04 23:19                 ` Benjamin Herrenschmidt
2005-11-03 15:58   ` Alan Cox
2005-11-03 15:30     ` Russell King
2005-11-03 16:23       ` Alan Cox
2005-11-04  3:35       ` Jeff Garzik
2005-11-04  3:35     ` Jeff Garzik
2005-11-04  8:43       ` Xavier Bestel
2005-11-03 14:58 ` Bartlomiej Zolnierkiewicz
2005-11-03 15:49   ` Alan Cox
2005-11-03 15:34     ` Bartlomiej Zolnierkiewicz
2005-11-04  0:14     ` Mark Lord
2005-11-04  0:17       ` Mark Lord
2005-11-04  1:18         ` Alan Cox
2005-11-04  3:49 ` Jeff Garzik
2005-11-05 22:31   ` Mark Lord
2005-11-04  6:43 ` Benjamin Herrenschmidt
2005-11-04  7:00   ` Jeff Garzik
2005-11-04 13:34   ` Alan Cox
2005-11-04 21:50     ` Benjamin Herrenschmidt
2005-11-06 20:41       ` Alan Cox

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=20051104231048.GD12026@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=benh@kernel.crashing.org \
    --cc=bzolnier@gmail.com \
    --cc=linux-kernel@vger.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